Folks:
I had to refactor log4j-plugin pom.xml to work with the new refactored
/src/ntdll/build.xml to compile and produce a viable artifact
Would appreciate a ping from the author to coordinate these changes to 1.2.16
or 1.2.17 distro
target mods for /src/ntdll/build.xml:
mc
windres
javah
src
>
> This might be helpful:
> http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook#MojoDeveloperCookbook-Creatingandresolvinganartifact
>
I think that's all deprecated now. Anybody know what the new way of
creating Artifacts and resolving them is?
>
> Benjamin
>
> --
There's a difference between the packaging type (car) and the file extension
(jar) so there's nothing to do actually.
That being said, there's already a 'car' type out there in Geronimo [1]. Are
you aware of this? If you want to add an official support in the ear plugin,
your packaging type should
Pablo wrote:
The behaviour i want is the same as the maven-ejb-plugin: Defines an ejb
packaging type but the artifact gets installed in the repo as a .jar and
gets bundled in the ear as .jar too.
The relevant magic is called an artifact handler. See [0] and look for
the EJB case.
Benjamin
Hi,
I am trying to come out with a plugin to detect and process JEE
application clients.
I created a new packaging type called 'car' through
META-INF/plexus/components.xml
(http://maven-car-plugin.googlecode.com/svn/trunk/maven-car-plugin/src/main/resources/META-INF/plexus/components.xml)
a
Thank you for your answer, but I have the same problem
I have the log ...
mvn clean eclipse:clean eclipse:eclipse -Declipse -Dlocalds install
-Dmaven.test.skip
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] e-Commerce Logistics ~ Project
[INFO] e-Commerce Lo
