[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Anita Kulshreshtha updated GERONIMO-2071:
-----------------------------------------
Attachment: configs.log
My xmlbeans pom is also autogenerated. I think(?) because the local tranql pom
has been flagged as invalid, maven looks for a valid pom in the repo, and may
be that is where stax is coming from -
(this is from the attached openejb.log)
[WARNING] POM for 'tranql:tranql:pom:1.3-SNAPSHOT:compile' is invalid. It will
be ignored for artifa
ct resolution. Reason: Not a v4.0.0 POM.
All the *-builders have to explicitly exclude
xmlbeans:xmlbeans-jsr173-api. It will be good to have it excluded at source.
The configs have always been working for me :) -
http://issues.apache.org/jira/browse/GERONIMO-2071#action_12414073
I am attaching configs.log generated for fresh checkout of rev. 411482 using
-
mvn -o -Dall=configs clean install >configs.log
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, configs.log, deploy-tool.patch,
> deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch,
> m2-plugins.patch, modules.patch, mvn.log, openejb.log, openejb.patch,
> openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851.
> (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and
> hence the migration work needs to be done here again. This JIRA will seek to
> consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches
> for migration will have to be applied on top of this one. This patch will
> contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851
> with links to dev list archives.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
