Cactus Maven Integration

[Christopher Lenz <cm...@gmx.de>]

Hi Vincent,

I'm wondering why the Cactus plugin for Maven is hosted in the Maven 
CVS-Repo instead of the Cactus repo (of course, I *do* see how many 
plugins for third-party applications Maven is hosting itself). Is there 
any chance that it could be moved into jakarta-cactus in the long term 
-- before a stable Maven release, for example?

The reason I'm asking is that I'm not actively involved in Maven 
development or even usage, so I have no idea what's going on with the 
Cactus plugin either, except I explicitly download Maven or browse the 
CVS change logs. I also suspect there are some discussions about Cactus 
on the Maven mailing lists that non-Maven users/devs like myself may be 
missing. Ideally, I think the Maven plugin should be hosted by us to 
avoid this fragmentation.

 From what I've seen, the Cactus plugin for Maven doesn't have any 
dependancy on the Ant integration, the configuration files and the logic 
for running tests in the various supported containers are mostly 
duplicated. This seems problematic when the two integration modules are 
hosted in different repositories.

Versioning is another problem, IIUC. We cannot currently release updates 
to the Cactus Maven Plugin outside of an update of Maven itself.

-chris



---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org

Re: Cactus Maven Integration

[Christopher Lenz <cm...@gmx.de>]

Hi Vincent,

thanks for the info. Don't agree about putting the integration modules 
into the product they integrate with, but hey ... ;-)

-chris

Vincent Massol wrote:
> Hi Chris,
> 
>>-----Original Message-----
>>From: Christopher Lenz [mailto:cmlenz@gmx.de]
>>Sent: 23 April 2003 10:52
>>To: Cactus Developers List
>>Subject: Cactus Maven Integration
>>
>>Hi Vincent,
>>
>>I'm wondering why the Cactus plugin for Maven is hosted in the Maven
>>CVS-Repo instead of the Cactus repo (of course, I *do* see how many
>>plugins for third-party applications Maven is hosting itself). Is
> 
> there
> 
>>any chance that it could be moved into jakarta-cactus in the long term
>>-- before a stable Maven release, for example?
> 
> 
> Everything is possible... Ok, here's the story
> 
> - Having it in Maven has been a huge success. Indeed, it has been
> packaged as part of Maven and thus readily available for all Maven
> users. Had it been separate, it would have been much harder to use
> 
> - That said, Maven is currently undergoing a refactoring which is
> separating the code from the plugins. The idea for the plugins is to be
> hosted in maven-plugins in cvs.apache.org. That said, the idea is also
> to have a mechanism to automatically upload plugins on demand from the
> Maven global remote repository (hosted on ibiblio.org). When this is
> available we would be in a position to decide whether we wish to get the
> plugin inside Cactus CVS or keep it in maven-plugins. For the time
> being, it would be viewed negatively by users.
> 
> - I think the end goal for Cactus is to become as ubiquitous as
> possible. For example, if one day we can get the Cactus plugin
> integrated into Eclipse, I think we should do it. Same applies for
> Maven. I'm strongly in favor of trying to get the Integrations located
> in the product they integrate with. In case it is not possible we can
> host is as we're doing today with most of the integrations.
> 
> 
>>The reason I'm asking is that I'm not actively involved in Maven
>>development or even usage, so I have no idea what's going on with the
>>Cactus plugin either, except I explicitly download Maven or browse the
>>CVS change logs. I also suspect there are some discussions about
> 
> Cactus
> 
>>on the Maven mailing lists that non-Maven users/devs like myself may
> 
> be
> 
>>missing. Ideally, I think the Maven plugin should be hosted by us to
>>avoid this fragmentation.
> 
> 
> Yes, that's correct but I think that's a way of life. There are
> discussions about Cactus on the turbine-dev mailing list too and in
> several other places. 
> 
> 
>> From what I've seen, the Cactus plugin for Maven doesn't have any
>>dependancy on the Ant integration, the configuration files and the
> 
> logic
> 
>>for running tests in the various supported containers are mostly
>>duplicated. This seems problematic when the two integration modules
> 
> are
> 
>>hosted in different repositories.
>>
> 
> 
> Wrong! :-) See
> http://maven.apache.org/reference/plugins/cactus/changes-report.html
> 
> The Cactus Maven plugin is a very lightweight wrapper around the Ant
> integration.
> 
> 
>>Versioning is another problem, IIUC. We cannot currently release
> 
> updates
> 
>>to the Cactus Maven Plugin outside of an update of Maven itself.
> 
> 
> See above. Plugins are being separated from Maven core and thus will
> have their own release cycles.
> 
> Thanks
> -Vincent



---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org

RE: Cactus Maven Integration

[Vincent Massol <vm...@pivolis.com>]

Hi Chris,

> -----Original Message-----
> From: Christopher Lenz [mailto:cmlenz@gmx.de]
> Sent: 23 April 2003 10:52
> To: Cactus Developers List
> Subject: Cactus Maven Integration
> 
> Hi Vincent,
> 
> I'm wondering why the Cactus plugin for Maven is hosted in the Maven
> CVS-Repo instead of the Cactus repo (of course, I *do* see how many
> plugins for third-party applications Maven is hosting itself). Is
there
> any chance that it could be moved into jakarta-cactus in the long term
> -- before a stable Maven release, for example?

Everything is possible... Ok, here's the story

- Having it in Maven has been a huge success. Indeed, it has been
packaged as part of Maven and thus readily available for all Maven
users. Had it been separate, it would have been much harder to use

- That said, Maven is currently undergoing a refactoring which is
separating the code from the plugins. The idea for the plugins is to be
hosted in maven-plugins in cvs.apache.org. That said, the idea is also
to have a mechanism to automatically upload plugins on demand from the
Maven global remote repository (hosted on ibiblio.org). When this is
available we would be in a position to decide whether we wish to get the
plugin inside Cactus CVS or keep it in maven-plugins. For the time
being, it would be viewed negatively by users.

- I think the end goal for Cactus is to become as ubiquitous as
possible. For example, if one day we can get the Cactus plugin
integrated into Eclipse, I think we should do it. Same applies for
Maven. I'm strongly in favor of trying to get the Integrations located
in the product they integrate with. In case it is not possible we can
host is as we're doing today with most of the integrations.

> 
> The reason I'm asking is that I'm not actively involved in Maven
> development or even usage, so I have no idea what's going on with the
> Cactus plugin either, except I explicitly download Maven or browse the
> CVS change logs. I also suspect there are some discussions about
Cactus
> on the Maven mailing lists that non-Maven users/devs like myself may
be
> missing. Ideally, I think the Maven plugin should be hosted by us to
> avoid this fragmentation.

Yes, that's correct but I think that's a way of life. There are
discussions about Cactus on the turbine-dev mailing list too and in
several other places. 

> 
>  From what I've seen, the Cactus plugin for Maven doesn't have any
> dependancy on the Ant integration, the configuration files and the
logic
> for running tests in the various supported containers are mostly
> duplicated. This seems problematic when the two integration modules
are
> hosted in different repositories.
> 

Wrong! :-) See
http://maven.apache.org/reference/plugins/cactus/changes-report.html

The Cactus Maven plugin is a very lightweight wrapper around the Ant
integration.

> Versioning is another problem, IIUC. We cannot currently release
updates
> to the Cactus Maven Plugin outside of an update of Maven itself.

See above. Plugins are being separated from Maven core and thus will
have their own release cycles.

Thanks
-Vincent

> 
> -chris
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org