ObjectWeb HOWL pom
--
Key: MEV-196
URL: http://jira.codehaus.org/browse/MEV-196
Project: Maven Evangelism
Type: Task
Components: Missing POM
Reporter: David Jencks
This is a valid m2 pom that is checked into the howl repo. However, AFAICT
[ http://jira.codehaus.org/browse/MEV-196?page=all ]
David Jencks updated MEV-196:
-
Attachment: pom.xml
This is the actual pom rather than a diff, since it is a new file.
ObjectWeb HOWL pom
--
Key: MEV-196
URL:
[ http://jira.codehaus.org/browse/MNG-699?page=comments#action_45803 ]
David Jencks commented on MNG-699:
--
I have no particular opinion on the idea of allowing you to change the
extension of the artifact generated by the jar plugin, but would like to point
[ http://jira.codehaus.org/browse/MEV-48?page=comments#action_43741 ]
David Jencks commented on MEV-48:
-
These are antique milestone releases that we aren't planning to ever look at
again. G1M4 should be out in a day or two and it uses a different way to
[ http://jira.codehaus.org/browse/MNG-581?page=comments#action_42733 ]
David Jencks commented on MNG-581:
--
Just including the generated classes in target/classes seems to be adequate for
m1. I think a fix for this is needed in m2. To me asking xmlbeans
[ http://jira.codehaus.org/browse/MAVEN-1634?page=comments#action_41996 ]
David Jencks commented on MAVEN-1634:
-
I fixed the backtick and some syntax errors in several project.xml's
Now I'm getting:
+
|
[ http://jira.codehaus.org/browse/MEV-8?page=comments#action_39773 ]
David Jencks commented on MEV-8:
Since there are non-sun freely available implementations of many of these specs
I would prefer to see the provenance (Sun) for these particular
