I've been trying to solve this exact same problem, it looks like a bug
in the release plugin, what version are you using.
On 15/10/2009 7:40 AM, Allan Ditzel wrote:
Really? Were you running it from the location the trunk was checked out? For
us, if we do a mvn release:prepare in the location of
Can you send us some build logs with -X enabled? There is nothing in
core that should be excluding aspectj, so something else is at play
here. And loading them with a different coordinate into your repo
manager is going to cause problems later, that is just patching the
symptoms
On Fri, Oct 23, 20
Hi Niall,
Niall Pemberton wrote:
> Merci Beaucoup - thats fixed it. Still not sure why it just started
> happening though.
It seems the version of the plugin is not locked:
%< =
~/src/Commons/proper/beanutils $ mvn versions:display-plugin-updates
[INFO] Scanning for pro
I have a multi-module project, only two modules, where Module-A creates a jar
during phase=package goal=jar using classifier=stubs. Module-B has it's only
dependency set to this stubs jar which Module-A creates. When I run the
top-level pom as 'maven package', all of Module-A gets created fine
Oh, I see... However, classpath I was referring to was just regular
classpath, not .classpath of eclipse... It's excluded from the regular
Java classpath as well for some reason.
Yaakov.
On Fri, Oct 23, 2009 at 3:57 PM, Nick Stolwijk wrote:
> The plugins have their own versioning. He means the 2
Le Fri, 23 Oct 2009 20:47:21 +0100,
Niall Pemberton a écrit :
> Merci Beaucoup - thats fixed it. Still not sure why it just started
> happening though.
>
You're welcome.
Have you try to clean your local repository ? this could fix your problem ?
> Niall
>
> On Fri, Oct 23, 2009 at 8:18 PM, To
The plugins have their own versioning. He means the 2.8 release of the
eclipse plugin.
Hth,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl
On Fri, Oct 23, 2009 at 7:42 PM, Yaakov Chaikin wrote:
> > This won't happen anymore in (unreleased) 2
Merci Beaucoup - thats fixed it. Still not sure why it just started
happening though.
Niall
On Fri, Oct 23, 2009 at 8:18 PM, Tony Chemit wrote:
> Le Fri, 23 Oct 2009 20:04:32 +0100,
> Niall Pemberton a écrit :
>
>> I'm getting the following error when I try to run mvn site on Commons
>> Beanuti
dded
> [WARNING] Not decrypting password for server 'releases' due to exception in
> secu
> rity handler.
> Cause: Given final block not properly padded
>
>
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error d
Le Fri, 23 Oct 2009 20:04:32 +0100,
Niall Pemberton a écrit :
> I'm getting the following error when I try to run mvn site on Commons
> Beanutils[1]
>
> I'm using maven 2.2.1 - it was working fine a week or so ago. I've
> been playing with maven 3.x though and have just switched back to
> 2.2.1,
On Tuesday, Nov 3rd at 8pm we'll be holding an Apache Maven meetup at
ApacheCon in Oakland, CA. The meetups are free and do not require
conference registration so if you're in the area, stop by.
The agenda and list of attendees is being maintained here[1] so please
login and add your name and agen
I'm getting the following error when I try to run mvn site on Commons
Beanutils[1]
I'm using maven 2.2.1 - it was working fine a week or so ago. I've
been playing with maven 3.x though and have just switched back to
2.2.1, so I'm wondering if thats the cause. Any ideas
I've searched the archives
Yeah I saw the posts on the dev list and have been following along.
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Friday, October 23, 2009 12:26 PM
To: Maven Users List
Subject: Re: Unexplained Animal Sniffer errors with JSPC plugin
just so you
> This won't happen anymore in (unreleased) 2.8. I agree with Barrie
> that this should be documented for users of 2.6 and 2.7. Anyone want
> to submit a patch for one of the help pages?
Version 2.8 of maven? I am running maven 2.0.9 which IS released...
>From what I see on the maven's page, the l
Yaakov,
This won't happen anymore in (unreleased) 2.8. I agree with Barrie
that this should be documented for users of 2.6 and 2.7. Anyone want
to submit a patch for one of the help pages?
Paul
On Fri, Oct 23, 2009 at 11:28 AM, Yaakov Chaikin
wrote:
> Wow.. That link is really an interesting re
With mvn dependency:tree I see it :
[INFO] | \- com.ontotext.owlim:big-owlim:jar:3.2.2:compile
If I change scope to compile in assembly I don't see it in the generated jar.
2009/10/23 Nick Stolwijk :
> Try running mvn help:effective-pom and mvn dependencies:tree to see if it
> really has the
Thankyou for your quick reply. Yes I am using maven 1.x only.
But I was able to make some progress but unfortunately found one more issue.
below is my maven goal
mohan in maven goal
and below is my build.xml:
]>
@sunny
Try running mvn help:effective-pom and mvn dependencies:tree to see if it
really has the appropriate scope.
Hth,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl
On Fri, Oct 23, 2009 at 6:43 PM, Alexander wrote:
> Only if dependency have an i
Only if dependency have an inappropriate scope.
2009/10/23 Laurent PELLEGRINO
> is it possible there is something in the jar library which indicates
> to maven that it cannot be assembly in one-jar ?
>
> 2009/10/23 Laurent PELLEGRINO :
> > yes it is :(
> >
> > 2009/10/23 Alexander :
> >> Does th
Hello All,
I'm trying to understand why token replacement doesn't take place on
files in src/main/webapp/WEB-INF. It works OK on files w/in
src/main/resources. Here's the config for maven-war-plugin:
org.apache.maven.plugins
maven-war-plugin
is it possible there is something in the jar library which indicates
to maven that it cannot be assembly in one-jar ?
2009/10/23 Laurent PELLEGRINO :
> yes it is :(
>
> 2009/10/23 Alexander :
>> Does this library declared in *dependencies* section?
>>
>> 2009/10/23 Laurent PELLEGRINO
>>
>>> I hav
Wow.. That link is really an interesting revelation to me... The crazy
thing is that nowhere in the output does it say that it's excluding
those jars. In fact, it just lists them as if they ARE included just
like that other jars...
But that link is only about Eclipse. What I don't understand is wh
yes it is :(
2009/10/23 Alexander :
> Does this library declared in *dependencies* section?
>
> 2009/10/23 Laurent PELLEGRINO
>
>> I have make again the jar-with-dependencies.xml step by step and
>> forced assembly version to 2.2-beta3 and it seems now it works...
>> However the library com.ontot
just so you know:
org.codehaus.mojoLanimal-sniffer-maven-plugin is blocked waiting for
maven-toolchains-plugin to be released
I intend trying to release maven-toolchains-plugin once I have confirmed
that I can release maven plugins (i.e. it will be the second plugin I will
try to release)
The fi
Sounds like you want an "exclude packages" option (or maybe granular
down to the class level) like JavaDoc.
Paul
On Fri, Oct 23, 2009 at 10:52 AM, Wayne Fay wrote:
> As always... if you do hack the source code, make it configurable and
> donate the changes back to Cobertura so it can be conside
Yes it's Kohsuke's original version since there's not a mojos release
yet.
It was a missing dependency. I hadn't thought of it that way since the
jspc compiler was added to catch compilation errors rather than being
used to ship the compiled jsp classes. Either way, in this case the
dependencies
As always... if you do hack the source code, make it configurable and
donate the changes back to Cobertura so it can be considered for
inclusion in a future release. This sounds like a potentially useful
feature for a number of organizations.
Wayne
On Fri, Oct 23, 2009 at 9:41 AM, Nick Stolwijk
Does this library declared in *dependencies* section?
2009/10/23 Laurent PELLEGRINO
> I have make again the jar-with-dependencies.xml step by step and
> forced assembly version to 2.2-beta3 and it seems now it works...
> However the library com.ontotext.owlim:big-owlim is never include in
> my j
I have make again the jar-with-dependencies.xml step by step and
forced assembly version to 2.2-beta3 and it seems now it works...
However the library com.ontotext.owlim:big-owlim is never include in
my jar. Even if I use the default jar-with-dependencies descriptor
which contains no exclude.
big-
OK, thanks everyone for these additional infos. I may stick with WTP
organisation then (using /WebContent/ instead of /src/main/webapp/) just for
convenience in Eclipse.
--
Vincent
baerrach wrote:
>
> On Fri, Oct 23, 2009 at 10:50 AM, Benson Margulies
> wrote:
>> An Eclipse project type, or
XY-orig
the module name does not have to match the artifactId
2009/10/23 Radim Kolar
>
> I have something like this:
>
>
> XY
>
>
> Is there way to tell maven that module XY is in subdirectory "XY-orig"
> instead of "XY" or subdirectory name must always match module name?
> --
> View this me
I think the changes to cobertura are not that much. And building and
deploying your own version of the cobertura-maven-plugin isn't hard either.
Take a look at cobertura's source [1], especially
generateSourceFile(SourceFileData sourceFileData)
[1]http://cobertura.svn.sourceforge.net/viewvc/cober
pache.maven.lifecycle.LifecycleExecutionException: Error deploying
artifact
: Failed to transfer file:
http://localhost:8085/archiva/repository/snapshots/co
m/effectivemaven/chapter01/simple-webapp/1.0-SNAPSHOT/simple-webapp-1.0-20091023
.135717-2.war. Return code is: 401
I have something like this:
XY
Is there way to tell maven that module XY is in subdirectory "XY-orig"
instead of "XY" or subdirectory name must always match module name?
--
View this message in context:
http://www.nabble.com/Is-there-way-to-specify-directory-for-module-in-master-pom--tp260
That might work. But my way was easier :)
And unless this changed recently, the cobertura report outputs the
source code files in the cobertura directory, not a subdir. I'm assuming
the OP has already shut off xref reports and other things which contain
source.
-Original Message-
From: St
or another technique would be to overwrite every html file that is in a
sub-dir with a simple html saying that the source code is confidential...
that way your links will still work ;-)
2009/10/23 Edelson, Justin
> Without an extensive amount of work, I suspect you could bind a custom
> executio
well that version of animal sniffer is Kohsuke's
I have not released the migrated to codehaus version yet
Looks like you are missing a dependency or two for your jar (probably
jasper-runtime and servlet-api)
-Stephen
2009/10/23 Jamie Whitehouse
> I recently discovered that animal sniffer wil
Without an extensive amount of work, I suspect you could bind a custom
execution of the clean plugin in the post-site phase to remove all the
html files from target/site/cobertura EXCEPT for index.html,
frame-packages.html, frame-summary.html, frame-sourcefiles.html, and
help.html. This would lead
> I have a build.xml and maven.xml. I am using the following goal into
> maven.xml to call ant:target in build.xml
It sounds like you're talking about Maven1 which means you're
essentially on your own. M1 is old, crusty, and not very many people
on this list are still using it which means you'll
Hi everyone.
I want to publish code coverage for my project on a public site but
some projects are not open source. How can I avoid cobertura to
publish the source code for each class leaving all the coverage
reports?
Thanks..
--
Daniele Dellafiore
http://ildella.net
http://twitter.com/ildella
Looks good. +1.
If default jar-with-all-dep works fine why don't you add your changes one by
one to determine what one actually is confusing assembly work?
2009/10/23 Nick Stolwijk
> Looks good. I don't really know what is going wrong.
>
> Just to be sure we are dealing with an assembly problem,
Looks good. I don't really know what is going wrong.
Just to be sure we are dealing with an assembly problem, but there are
classes in your target/classes directory after you have run mvn clean
assembly:assembly?
Could you also take a look at the logging of the assembly plugin, maybe even
with -
I use the following :
>
> maven-assembly-plugin
>
> ${pom.artifactId}-${pom.version}
>
> src/main/assembly/jar-with-dependencies.xml
>
>
>
>
> package
>
> single
>
>
>
>
2009/10/23 Nick Stolwijk :
> That should be the right syntax. How did you configure your pom wrt the
> assembly plu
That should be the right syntax. How did you configure your pom wrt the
assembly plugin?
With regards,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl
On Fri, Oct 23, 2009 at 2:55 PM, Laurent PELLEGRINO <
laurent.pellegr...@gmail.com> wrote:
Thanks for links.
I have succeeded to generate a jar which contains the file I wanted.
However I have an another problem by editing the default
jar-with-dependencies.xml : the jar generated contains all
dependencies in but not the binaries (.class) of the project from
where I launch the mvn assemb
Neil Chaudhuri wrote:
A colleague at work expressed an interest in doing a lot of Maven-like things in the JavaScript realm. I did some research and discovered the Maven JavaScript plugin. It looks neat, but it is an alpha version and seems to have little activity.
I was simply hoping to find s
We're using it at my workplace. We have our own "released' version just to
stop the plugin update check from happening so frequently.
I think the plugin is strong for creating javascript artifacts and keeping
them separate. If you pair it with the jetty-maven-plugin, you can get away
with a pure
On 22 Okt 2009, Neil Chaudhuri wrote:
> A colleague at work expressed an interest in doing a lot of Maven-like things
> in the JavaScript realm. I did some research and discovered the Maven
> JavaScript plugin. It looks neat, but it is an alpha version and seems to
> have little activity.
>
>
Hi All,
I have a build.xml and maven.xml. I am using the following goal into
maven.xml to call ant:target in build.xml
mohan
My Issue is: when I run ejb.test goal, It's failing to recognize the
classpaths/properties which are defined
49 matches
Mail list logo
