Yes, you're absolutely right. Changing to env.JBOSS_HOME did the trick. It
now works with 2.0.10-RC9.
There must have been some kind of bug in the older maven releases that
made it work without the pre env..
Thanks,
/Anders
davidkarlsen wrote:
On Wed, 20 Aug 2008, Anders Hammar wrote:
Hi,
Turns out that it works if I use the (correct) notation of env.JBOSS_HOME.
I'm not sure if you still want to investigate? If so, I could fila a jira
for you.
In any case, below is the non-working pom if you want to check it out:
project xmlns=http://maven.apache.org/POM/4.0.0;
They indeed both give the same result, but not what I was expecting.
I was hoping to get:
+ parent
+ target
+ parent-1.0-SNAPSHOT-assembly
+ modules
+ module1
+ module1-1.0-SNAPSHOT-assembly.zip
+ module2
And what command did you exactly execute?
It should be mvn install:install-file -DgroupId=javax.transaction
-DartifactId=jta -Dpackaging=jar -Dversion=1.0.1B
-Dfile=your-jar-filename
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
On Thu, Aug
Hi there,
I encountered a strange problem. Since a few weeks I'm not able to perform a
release with Maven. The release process fails during executing the
release:prepare goal at the same position, always. The point at which the
release fails is when Maven tries to commit the release POM's to SVN.
Hi all,
One of my ant based project output is a sar file.
A sar file for phoenix avalon container is simply a zip/jar file
including jars and any configuration file needed.
Using the maven-assembly-plugin I have been able to generate a zip
including everything I need, but it is named zip and
I already answered your question 2 days ago:
http://markmail.org/message/qixvhtloug5rlmkz
Please just follow up the original thread rather than reposting a copy-paste.
Thanks,
Brett
2008/8/21 Stefano Bagnara [EMAIL PROTECTED]:
Hi all,
One of my ant based project output is a sar file.
A sar
Brett Porter ha scritto:
I already answered your question 2 days ago:
http://markmail.org/message/qixvhtloug5rlmkz
Please just follow up the original thread rather than reposting a copy-paste.
I apologize! Both, my message and your answer was in my spam filter and
I thought my message never
Brett Porter ha scritto:
Check out the attach goal here:
http://mojo.codehaus.org/build-helper-maven-plugin/usage.html
I know the build-helper plugin, but I don't understand how it can help here.
My issue is creating a zip file with a sar extension.
From my understanding the build-helper
If your on Mac OS 10.5, check out
http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/
On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:
Hi there,
I encountered a strange problem. Since a few weeks I'm not able to
perform a
release
No, we use MS Windows Vista, and XP. The problem occurs on each of these
platforms.
-Ursprüngliche Nachricht-
Von: Luke Daley [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 21. August 2008 11:12
An: Maven Users List
Betreff: Re: Release fails during SVN commit
If your on Mac OS 10.5,
Hi all,
I've been given the task of maintaining an exisiting Hudson/Maven setup. I
think i've got an 'ok' understanding of whats going on but i'm still
learning daily.
The problem I have is this. I have a multi-module build that checksout a
project from a cvs repository, builds the source,
Yes, of course - hopefully in Java 7! A warning in the documentation would be
handy!
Didn't try assembly:directory but surely it also needs to copy/recognise links
so won't work either, so only way I can see is to drop into OS or ant symlink.
I have an install script so simply changed it to
Hi Jeff,
Try the following:
After the /plugins add this
sourceDirectoryJAVA_SOURCE_DIRECTORY/sourceDirectory
outputDirectorytarget/classes/outputDirectory
testOutputDirectorytarget/testclasses/testOutputDirectory
resources
resource
It was exactly that command:
mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta
-Dpackaging=jar -Dversion=1.0.1B
-Dfile=C:/.m2/repository/javax/transaction/jta/1.0.1B/jta-1.0.1B.jar
Is that right, isn´t ?
Nick Stolwijk-4 wrote:
And what command did you exactly execute?
Hi,
Sorry I post a java question in this mailing list. I know you guys know the
answer.
I want to create a classdomain.Customer, and domain.Order so that the
other class can useimport statement to reference this 2 classes.
eg. import domain.Customer;
import domain.Order;
Where
2008/8/21 Stefano Bagnara [EMAIL PROTECTED]:
Brett Porter ha scritto:
Check out the attach goal here:
http://mojo.codehaus.org/build-helper-maven-plugin/usage.html
I know the build-helper plugin, but I don't understand how it can help here.
My issue is creating a zip file with a sar
Is there any standard java api (e.g. using Maven Dependency Plugin api if
any) for getting a full dependency tree from a pom ?
thanks for any hint
Christian-luc
--
View this message in context:
http://www.nabble.com/Maven-API-for-dependency-resolution-tp19087867p19087867.html
Sent from the
I've had the problem as well on Ubuntu Linux, so it's a general problem with
SVN 1.5.
-Stephen
On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke [EMAIL PROTECTED]wrote:
No, we use MS Windows Vista, and XP. The problem occurs on each of these
platforms.
-Ursprüngliche Nachricht-
Hi,
I have maven2 and eclipse 3.4 in my windows vista system.
I tried to run the following mvn command, but got some error. I belileve it
is a version issue.
d:\workspacemvn archetype:create -DarchetypeGroupId=org.springframework.ws
-Dar
chetypeArtifactId=spring-ws-archetype
Hi Stephen,
thank you for your answer.
Can anyone else confirm this? So one (probably me) should report this issue at
the issue tracker.
Andreas.
-Ursprüngliche Nachricht-
Von: Stephen Duncan Jr [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 21. August 2008 14:48
An: Maven Users
I had the same problem with 1.5.1 on Gentoo.It's a subversion problem, not
a release plugin problem.If you run the same command that release is
trying to run (can be seen when you run mvn with -X), it fails. Basically,
with 1.5, you apparently cannot svn cp your working copy into a
On Thursday 21 August 2008 8:39:30 am houzecl wrote:
Is there any standard java api (e.g. using Maven Dependency Plugin api if
any) for getting a full dependency tree from a pom ?
thanks for any hint
groupIdorg.apache.maven.shared/groupId
artifactIdmaven-dependency-tree/artifactId
On the other hand, the fact that I forgot to run svn up before running the
release plugin has bitten me before, and I had to make a second release
because I didn't realize it. Ideally it'd warn you about remote changes the
same way it does about local uncommitted changes. But that still leaves
On Thursday 21 August 2008 10:09:07 am Stephen Duncan Jr wrote:
On the other hand, the fact that I forgot to run svn up before running the
release plugin has bitten me before, and I had to make a second release
because I didn't realize it. Ideally it'd warn you about remote changes
the same
The issue is discussed on the subversion users list :
http://www.nabble.com/Mac-OS-X-%2B-SVN-1.5.1-%3D-Branch-problem-td19017538.html
It is related to a change in JavaHL:
* correctly set the peg revision for copy in JavaHL (r31994)
Emmanuel
On Thu, Aug 21, 2008 at 4:15 PM, Daniel Kulp [EMAIL
If it's happening directly from the command-line as Daniel indicated (I
haven't tried it myself, but as far as I know Maven uses the command-line,
not JavaHL), then it can't be a JavaHL issue.
-Stephen
On Thu, Aug 21, 2008 at 10:38 AM, Emmanuel Venisse
[EMAIL PROTECTED] wrote:
The issue is
Hi there,
I have an issue with maven classpath generation (mvn eclipse:eclipse)
for eclipse.
I have 3 independent projects (say A, B and C) with no common root.
Project A is the common project (jar) which project B and C will
include.
In pom.xml in project B and project C, there is a
Yes, maven-scm use the command line.
I extracted the JavaHL comment from the thread on the svn users list, and I
don't know if some other part was impacted with this change
Emmanuel
On Thu, Aug 21, 2008 at 4:45 PM, Stephen Duncan Jr [EMAIL PROTECTED]
wrote:
If it's happening directly from the
Does your POM have any SVN keyword substitutions in it? For example $Id$ or
$Revision$? I have had issues with releases that at the root was a file
locking problem that I was able to alleviate by removing the keywords
substitutions.
-Nathan
-Original Message-
From: Andreas Heinecke
The -Dfile= bit is wrong. By specifying it that way, you are writing
the file to the same place you are reading it from. The jar might even
be corrupt now -- check it with Winzip.
Instead, put the file in say c:/temp and specify
-Dfile=C:/temp/jta-1.0.1B.jar. Then Maven will copy it to the proper
I have an existing multi-module project that I want to integrate Visual
Paradigm into. What I would like to do is:
1. Reverse engineer our existing code base
2. Forward Engineer from our model
3. Display generated site artifacts with our Documentation from Maven.
Has anyone done this
envars are definitely supposed to be prefixed by env. at all times. I
suspect you were exploiting a bug in the interpolator prior to this.
-john
Anders Hammar wrote:
Hi,
Turns out that it works if I use the (correct) notation of env.JBOSS_HOME.
I'm not sure if you still want to investigate?
using the workspace property the eclipse plugin can find references to
others projects and link them.
Otherwise without having an inheritence but a reactor pom with 3 modules
will also link them together.
On Thu, Aug 21, 2008 at 4:51 PM, Lam Hayward [EMAIL PROTECTED]wrote:
Hi there,
I have an
I have the same issue on Leopard with svn 1.5
As a workaround I have to checkout the trunk of the project just before to
do the release and it works.
Arnaud
On Thu, Aug 21, 2008 at 5:07 PM, Beyer,Nathan [EMAIL PROTECTED] wrote:
Does your POM have any SVN keyword substitutions in it? For
You need to be careful with your spelling:
-DarchetypeVesrion=1.0.0
This should be -DarchetypeVersion, not Vesrion. I believe it will work
once you fix this.
Wayne
On 8/21/08, sam wun [EMAIL PROTECTED] wrote:
Hi,
I have maven2 and eclipse 3.4 in my windows vista system.
I tried to run
yes it was an existing bug/feature I already see before.
If 2.0.10 become 2.1.0 the support of env vars without env. prefix can be
removed because I think we already said a long time ago that it was a bug
and not a feature ...
Arnaud
On Thu, Aug 21, 2008 at 7:52 PM, John Casey [EMAIL PROTECTED]
I'm writing a custom enforcer rule to enforce that my build contains no
snapshot dependencies. I only want to run the rule in a profile call
'release'. But since I'm already using the enforcer plugin in my build
outside the profile it can't find my custom rule if I declare the plugin
dependency
Hi Nathan,
no there are no keyword substitutions. It seems to be a SVN bug, or changed
behaviour maybe.
-Andreas.
-Ursprüngliche Nachricht-
Von: Beyer,Nathan [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 21. August 2008 17:07
An: Maven Users List
Betreff: RE: Release fails during SVN
As the discussion pointed by Emmanuel shows the root of the problem is the SVN
1.5.1 client software. I can't say if it is a bug or a changed behaviour, refer
to the discussion and further documentation on the new features of SVN 1.5.1 to
decide this.
The important hint is that this problem
I use Windows Vista SP1, Sun JDK 5u16, Maven 2.0.9 and SVN 1.5.1 (built by
SlikSVN [1]) and an SVN HTTP-based Server at 1.5.1, and have performed two
releases recently with no issues.
[1] http://www.sliksvn.com/en/download/
-Original Message-
From: Andreas Heinecke [mailto:[EMAIL
Well, I used Vista SP1, JSK 1.6.0_10, Maven 2.0.9 and SlikSVN 1.5.1 (I also
tried CollabNet SVN 1.5.1) and a 1.5.0 SVN server. Nothing worked until I used
a 1.4.6 client.
-Original Message-
From: Beyer,Nathan [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 21, 2008 8:52 PM
To: Maven
I tried setting the following properties in pom.xml or command line:
workspace
eclipse.workspace
maven.eclipse.workspace
The command does not report any error. However, the eclipse buildpath of
project B or project C still do not reference project A.
Any idea?
-Original Message-
From:
You need to configure the eclipse plugin as Arnaud said:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
It will be something like:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
configuration
My current solution, since this declaration is being made in a parent pom, is
to declare the plugin with the custom rule dependency in the parent's build,
and then the execution in the profile named 'release'. This allows children
to define additional executions while preserving the dependency
On Thu, Aug 21, 2008 at 9:51 AM, Lam Hayward [EMAIL PROTECTED] wrote:
Hi there,
I have an issue with maven classpath generation (mvn eclipse:eclipse)
for eclipse.
I have 3 independent projects (say A, B and C) with no common root.
Project A is the common project (jar) which project B and C
hi
I try to start with maven and I'm sinking in tons of documentation.
Docs are a good thing, but I somehow miss the very obvious.
Right now I'm going through a the nice manual calling Better Builds
with Maven. Basically I ran the following commands:
$mvn archetype:create
On Fri, 22 Aug 2008 08:28:36 Andrew Close wrote:
On Thu, Aug 21, 2008 at 9:51 AM, Lam Hayward [EMAIL PROTECTED]
wrote:
Hi there,
I have an issue with maven classpath generation (mvn eclipse:eclipse)
for eclipse.
I have 3 independent projects (say A, B and C) with no common root.
Hi Wessie,
why not simply upload the ear file to a location outside the cvs which
is accessible via web (or via scp)? By the way, I was glad when we
switched from CVS to SVN. I'm not an expert, but I have the impression
that SVN is much more stable. Nevertheless I wouldn't put constantly
See http://mojo.codehaus.org/exec-maven-plugin/java-mojo.html
Ben Jakbot wrote:
hi
I try to start with maven and I'm sinking in tons of documentation.
Docs are a good thing, but I somehow miss the very obvious.
Right now I'm going through a the nice manual calling Better Builds
with Maven.
I copied the jta jar file to my C: folder and installed this way:
mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta
-Dpackaging=jar -Dversion=1.0.1B
-Dfile=C:/jta-1.0.1B.jar
When trying to append the hibernate dependency to pom.xml, the following
message appears:
Error
51 matches
Mail list logo
