[jira] Commented: (CACTUS-137) Building maven plugin should be easier

[ca...@jakarta.apache.org]

The following comment has been added to this issue:

     Author: Vincent Massol
    Created: Mon, 30 Aug 2004 1:42 PM
       Body:
Hi Felipe,

Cool. Thanks for the patch. I was about to apply it when I noticed you've used a build.properties file. I'm reserving this file for user specific environmental variable only and it should never be checked in (hence the cvsignore). If the properties are supposed to be shared and I suppose they are, then they should go in project.properties.

Ok with this? :-)

Thanks
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/CACTUS-137?page=comments#action_37930

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/CACTUS-137

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CACTUS-137
    Summary: Building maven plugin should be easier
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Cactus
 Components: 
             Maven Integration
   Versions:
             1.7

   Assignee: 
   Reporter: Felipe Leme

    Created: Wed, 25 Aug 2004 5:58 AM
    Updated: Mon, 30 Aug 2004 1:42 PM

Description:
Building the maven integration plugin should be an automated task - right now, the developer must manually copy jars to his local maven repo.

Ideally, the whole Cactus should be build with Maven, but while that doesn't happen, we need a workaround. We have at least 2 options:

1.Modify root's build.xml to copy the JARs to the local repo
2.Modify maven.xml on integration/maven to do both jobs.

Each approach has its advantages and disadvantages:

Ant approach
------------

- D: requires a lot of Ant coding (once you get used to Maven, is hard to bo back to the task of writing Ant targets :-)
- D: it needs to check if user has maven installed, if $MAVEN_REPO, exists, etc...
- A: the process would be transparent for the maven integration module

Maven approach
--------------

The main issue with the Maven approach is that we have a chicken-egg p roblem: we would be copying the jars to the repo using maven, but maven wouldn't run because the dependencies check would fail. The solution would be overriding the jars on build.properties and creating  a postGoal on plugin:install to copy the jars.

- A: easier to implement
- A: the process would be isolated to the maven integration module
- D: overriding the jars is kind of a hack solution


If we opt for the maven approach, I can work on a patch (well, I could do the same for the Ant approach too, but I rather not touch those evil scripts :-)



 








---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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