Anyone? :-)
-Ursprüngliche Nachricht-
Von: Lewis, Eric [mailto:eric.le...@ipi.ch]
Gesendet: Mittwoch, 14. Dezember 2011 11:20
An: users@maven.apache.org
Betreff: Use mvnsh with already installed Maven - how?
Hi
I'm looking into mvnsh right now, after having installed Maven 3.0.3
Is
The poms for my A and B projects had each a dependency to an external
library (let's call them respectively AExt and BExt). I excluded there the
dependency to xerces and now the project compiles.. The question is if this
will have side-effects which I couldn't notice yet... Let's see.. ;)
Thanks
On Mon, Dec 19, 2011 at 6:34 PM, Lewis, Eric eric.le...@ipi.ch wrote:
Anyone? :-)
Try the people that build mvnsh
http://shell.sonatype.org/index.html
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional
Hi,
i would like to add a line into my manifest.mf when the .jar is created
with netbeans 7.0.1.
This is my pom.xml:
profiles
profile
idbuild-for-felix/id
dependencies
dependency
groupIdorg.apache.felix/groupId
Why aren't you using the standard Maven way for a jar project and
configure the jar plugin?
http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html
/Anders
On Mon, Dec 19, 2011 at 11:56, Oliver Zemann
oliver.zem...@googlemail.com wrote:
Hi,
i would like to add a
Because Netbeans created it that way... and in the netbeans created
pom.xml there's no usage of the maven-jar-plugin. Also the statement:
Starting with version 2.1, the maven-jar-plugin uses Maven Archiver
2.1. This means that it no longer creates the Specification and
Implementation details in
On Friday 16 December 2011 Anders Hammar wrote:
Using dependencyManagement in the parent to specify the version of
dependencies is also an option. IMHO that's the true Maven way, but
Ron's approach could be an option in some cases. I don't like that
approach though as it will create an
2011/12/19 Oliver Zemann oliver.zem...@googlemail.com
I dont want to change so much in the pom.xml, because i am new to maven
and dont want to kill it, so i hoped there is something like just add
this line and its done ;)
It's wrong. It's better to use the correct Maven plugin. There's a
Hi,
I'm using Maven 1.0 to generate the ear and deploy it in JBoss 4.0.
The issue I'm facing is, the java module entries in
ear/META-INF/application.xml are incorrect. I have placed all jars inside a
'library' folder under the ear. But in application.xml, only the name of the
jar is
mentioned
I'm using Maven 1.0 to generate the ear and deploy it in JBoss 4.0.
... Any help is appreciated.
Are you honestly still using Maven 1? If so, you're pretty much on
your own at this point.
You really need to upgrade to Maven2 or ideally Maven3.
Wayne
The problem is this code has been there for 6 years and no investment has
been made for any kind of upgradation. Also, we are kind of moving into auto
pilot mode shortly and need to make certain changes before setting it on
auto pilot.
So I really need this solution to move on to other things
The problem is this code has been there for 6 years and no investment has
been made for any kind of upgradation. Also, we are kind of moving into auto
The most pragmatic solution is most likely download the source code
to Maven1 and the plugins we are using, find the line(s) that need to
be
On 11-12-19 07:56 AM, Wayne Fay wrote:
I'm using Maven 1.0 to generate the ear and deploy it in JBoss 4.0.
... Any help is appreciated.
Are you honestly still using Maven 1? If so, you're pretty much on
your own at this point.
You really need to upgrade to Maven2 or ideally Maven3.
Wayne
Wayne Fay wrote:
The problem is this code has been there for 6 years and no investment has
been made for any kind of upgradation. Also, we are kind of moving into
auto
The most pragmatic solution is most likely download the source code
to Maven1 and the plugins we are using, find the
I cannot be able to read
i dont understand that.
Netbeans uses the felix-maven-plugin by default. And yes, i am using it
too. But what has this to do with my problem in adding a line to the
manifest.mf? On the site you posted, i only found that:
If you have an existing manifest, you can add
Hi,
I was trying to port my ant project with JNI over to maven and I
encountered a problem with maven-antrun-plugin with an error message:
“Can’t load javah”.
Here are the details:
I have an ant build script that also generates jni files using ant’s javah
task. I try to port it to maven,
I have a webapp project under eclipse by my colleage. So it has WEB-INF/lib
directory
and dependcy packages are put in by my colleage.
Now I have create a pom file for the project. But import the maven project
, I also need to configurate the classpath for it through
project --properties--Java
17 matches
Mail list logo
