|
| Re: IAM-based Maven actor and Maven plugin [message #27865 is a reply to message #27825] |
Tue, 11 November 2008 09:36   |
|
Hi Ismael,
That's a good question. Looking at the direction of the integration (in one case,
Buckminster using Maven functionality, and in the other case the opposite), one could
argue that the Maven plug-in belongs to Buckminster and the Buckminster actor belongs to
Maven. On the other hand, if you really want to integrate between the two, chances are
high that you'd want both so perhaps they should be bundled in the same
"maven-buckminster" integration feature.
The most practical solution for you right now is probably to keep the actor code in a
place where you have committer rights. Are you a committer to the IAM project? Where is
the code right now?
I'm all for integrating this with the Buckminster project once the actor is dependent on
IP approved libraries. If I've undestood it correctly, the approval process for the Maven
jars is in progress.
In any case, I think you should add a Bugzilla to Buckminster with a pointer to you wiki
page so we have a common place to track progress.
Regards,
Thomas Hallgren
Ismael Teijeiro Florez wrote:
> Hi,
>
> As a part of my Master Thesis work I'm developing a Maven actor
> (http://wiki.eclipse.org/IAM_Buckminster_Maven_Actor) and a Maven plugin
> for Buckminster using the IAM libraries (http://wiki.eclipse.org/IAM).
> There's no bugzilla for the actor, but there is
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=178695 for the Maven plugin.
> Would you find it interesting to include in Buckminster both the actor
> and the Maven plugin or would you prefer them to remain as IAM plugins?
> (at least at the moment)
>
> Regards, Ismael
>
|
|
|
| Re: IAM-based Maven actor and Maven plugin [message #27905 is a reply to message #27865] |
Tue, 11 November 2008 10:07 |
 Ismael Teijeiro Florez
Messages: 12
Registered: July 2009 |
Junior Member |
|
|
Hi,
> Hi Ismael,
> That's a good question. Looking at the direction of the integration (in one
case,
> Buckminster using Maven functionality, and in the other case the opposite),
one could
> argue that the Maven plug-in belongs to Buckminster and the Buckminster
actor belongs to
> Maven. On the other hand, if you really want to integrate between the two,
chances are
> high that you'd want both so perhaps they should be bundled in the same
> "maven-buckminster" integration feature.
> The most practical solution for you right now is probably to keep the actor
code in a
> place where you have committer rights. Are you a committer to the IAM
project? Where is
> the code right now?
I'm not a committer to the IAM project at the moment. I think I should do
a few more contributions (the actor and the Maven plugin for Buckminster,
indeed) before beginning the process of becoming an IAM committer.
Answering your other question, the code is in my computer (I didn't want
to just upload it to IAM without saying anything here :-) )
I agree with you that keeping both plugins in IAM would be the most
practical thing right now (for example I'm following the IAM guidelines in
my code, so I wouldn't have to adapt anything). And it might be easier for
me to become a commiter doing it like this (correct me if I'm wrong)
because I have already contributed to IAM with a full new plugin
(http://wiki.eclipse.org/IAM_Buckminster_Integration), several patches and
two wiki pages.
> I'm all for integrating this with the Buckminster project once the actor is
dependent on
> IP approved libraries. If I've undestood it correctly, the approval process
for the Maven
> jars is in progress.
> In any case, I think you should add a Bugzilla to Buckminster with a pointer
to you wiki
> page so we have a common place to track progress.
Ok, I'll post the link to the Bugzilla when I add it.
By the way, I'll be in Ludwigsburg next week for the Eclipse Summit, so we
might have a chance to talk in person about all this stuff (and maybe do a
little demo in the computer).
Regards,
Ismael
|
|
|
|
Powered by
FUDForum. Page generated in 0.02675 seconds
] 
Search
Help
Register
Login
Home
