[
http://issues.apache.org/jira/browse/GERONIMO-1672?page=comments#action_12369267
]
Jacek Laskowski commented on GERONIMO-1672:
-------------------------------------------
Well, I'm a little confused with how M2 works. It seems I need to stand up,
take a walk and think about it without sitting in front of the code ;) The
situation is that the version of the plugin is already specified in the parent
pom.xml:
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.1.3-SNAPSHOT</version>
</plugin>
So, I'd expect that whenever I use the plugin in the child poms that particular
version is used as well. I'll need to test it out and ask on the Maven user
mailing list.
The derby unit test fails because depending on how you run M2 the current
working directory is either the top directory of Geronimo or module/derby. The
test should be fixed as it slows down the migration (don't have an idea how,
though).
Other than the test in the derby module, do you see any troubles? The xmlbeans
jsr173 lib should already be commented out and not used during the build. Make
sure you use Maven 2.0.2 and don't build plugins locally. Strange things will
happen for other people who attempt to use M2 to build Geronimo. You
experienced it, actually, didn't you? ;)
> Migrate security module to M2
> -----------------------------
>
> Key: GERONIMO-1672
> URL: http://issues.apache.org/jira/browse/GERONIMO-1672
> Project: Geronimo
> Type: Task
> Components: security
> Versions: 1.x
> Environment: All
> Reporter: Anita Kulshreshtha
> Assignee: Anita Kulshreshtha
> Fix For: 1.x
> Attachments: pom.patch
>
--
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
