On Thu, Jun 2, 2016 at 11:25 AM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
> http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html
>
> On 2 June 2016 at 07:22, Jorg Heymans <jorg.heym...@gmail.com> wrote:
>
> > Hi,
&
rba...@gmx.de>
wrote:
> BTW: What also comes to my mind.
>
>
> Does the same happen if you ran that project as a freestyle project
> instead of Maven Job type (which i assume) ?
>
>
> Kind regards
> Karl Heinz Marbaise
> On 6/1/16 8:04 PM, Karl Heinz Marbaise wrote:
>
Hi,
I am trying to pinpoint a performance issue we are incurring with maven
under Jenkins. Basically what we are seeing is that maven is taking a very
long time getting past the initial 'Scanning for projects' message. As you
can see in below snippet, more than half a minute elapses before the
On Fri, Jul 9, 2010 at 7:55 AM, Ralph Goers ralph.go...@dslextreme.comwrote:
According to MarkMail the only posts she has ever made are those to inform
us she is out of the office.
Lurking is a constitutional right of the interwebs Ralph :-)
Jorg
On Fri, Feb 19, 2010 at 11:29 AM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
It turns out that the biggest blocker in achieving /any/ reliable
concurrent building within maven is the java file system, which is basically
seems limited to single threaded visibility of file updates;
On Thu, Dec 3, 2009 at 7:44 PM, Brian Fox bri...@infinity.nu wrote:
Something like duplicate dependencies likely means you have a real
problem you didn't know about in your poms. I think failing is
appropriate in this case.
I fail to grok what you just said there. So if i have in my pom
On Tue, Dec 1, 2009 at 9:49 PM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
I am pleased to announce that the weave mode now does a
mvn clean install of a fairly regular project with any number of
threads, and at great speed improvement - 2-4x is not uncommon.
There are still
On Tue, Nov 24, 2009 at 12:18 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Jorg Heymans wrote:
[ERROR] The project build-tools:1-SNAPSHOT
(D:\src\myproject\pom.xml) has 1 error
[ERROR]
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
must
On Thu, Dec 3, 2009 at 11:10 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
2009/12/3 Jorg Heymans jorg.heym...@gmail.com
On Tue, Nov 24, 2009 at 12:18 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Jorg Heymans wrote:
[ERROR] The project build-tools:1-SNAPSHOT
Tried it out on our project, and i'm getting this:
[ERROR] The project build-tools:1-SNAPSHOT
(D:\src\myproject\pom.xml) has 1 error
[ERROR]
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
must be unique: junit:junit:jar - duplicate declaration of
Hi Dan,
Would the multithreading feature make it easier or harder to implement
something like [1], ie distribute the different modules of a reactor
build across different machines ? Or is it completely unrelated you
think ?
Thanks,
Jorg Heymans
[1]
http://n4.nabble.com/New-plugin-to-distribute
On Wed, May 27, 2009 at 3:55 PM, Christian Edward Gruber
christianedwardgru...@gmail.com wrote:
Anyway, I'm +1 on this. It is clear, unambiguous, and terse. Those work
for me.
My thoughts exactly !
Jorg
-
To unsubscribe,
On Wed, Apr 1, 2009 at 9:24 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
Is it a release of a project which doesn't have a scm element and use
a released parent project which has one ?
That's the exact situation yes. Is this no longer an accepted
situation perhaps ?
Jorg
Hi,
beta-9 seems to have introduced something which my project cannot
grok. I'm trying to do a release of my project's main pom:
$mvn release:prepare -N -Darguments=-N
[INFO]
[ERROR] BUILD FAILURE
[INFO]
On Wed, Apr 1, 2009 at 9:33 AM, Olivier Lamy ol...@apache.org wrote:
Try mvn help:effective-pom I'm not sure the scm information is correct.
I don't know what to make from the scm info, in any case it points to
a non-existing tag:
scm
/maven/apache-maven/2.1.0/)
Works fine (and a tad bit faster) for my project builds. FWIW I don't
see any of the [WARNING] messages Daniel is seeing.
Regards,
Jorg Heymans
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
On Wed, Sep 10, 2008 at 5:32 AM, John Casey [EMAIL PROTECTED] wrote:
Hi,
I've fixed MNG-3748, where illegal elements in the settings.xml were not
triggering build failure. Anyway, this release candidate includes a fix for
that issue:
On Fri, May 9, 2008 at 10:34 AM, Jason van Zyl [EMAIL PROTECTED] wrote:
Hi,
For those not at JavaOne I just wanted to mention that Kohsuke along with
the Hudson community won a Duke award. I think Hudson is awesome and Kohsuke
has done a great job supporting the community (just read the
Just used it to build and release about 10 modules in my project, worked
fine.
Thanks for the consistence in quality btw, the RC process is really a step
up from what was done before.
Jorg
On Tue, Apr 1, 2008 at 11:34 PM, Brian E. Fox [EMAIL PROTECTED]
wrote:
We made a minor tweak to the
same here, no apparent issues with RC4 on my projects.
On Thu, Mar 27, 2008 at 9:27 AM, nicolas de loof [EMAIL PROTECTED] wrote:
+1
Tested with my local projects with no issue.
2008/3/26, Raphaël Piéroni [EMAIL PROTECTED]:
+1 the bundle worked fine to build
the archetype plugin.
(sorry for hijacking the vote thread for this)
Hi Raphaël,
Can you give us some pointers to list threads, proposals or specs that
explain the basics of the new architecture and how to use it ? I'm very keen
to try it out and give you all the feedback you want, but if it means
grepping the
+1000, thanks Raphaël !
Jorg
On Jan 8, 2008 11:58 PM, Raphaël Piéroni [EMAIL PROTECTED] wrote:
Hello,
I would like to prepare the alpha-1 release of the archetypeng stuff.
Preparing that release will need to do these things:
1. move the current archetype code
On Jan 8, 2008 11:02 PM, Tom Huybrechts [EMAIL PROTECTED] wrote:
Take a look at the developer cookbook (
http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook )
It would make sense to create a link from
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html to
FYI a release seemed to be eminent a while ago [1], but it never
materialized somehow :-(
Jorg (another eager archetypeNG customer)
[1] http://thread.gmane.org/gmane.comp.jakarta.turbine.maven.devel/82488
On Jan 4, 2008 1:04 AM, Brian E. Fox [EMAIL PROTECTED] wrote:
The archetypeNG plugin
I guess the dependency plugin itself now needs another release before I can
do mvn dependency:tree on a project ?
Regards
Jorg
On Dec 17, 2007 10:07 PM, Brian E. Fox [EMAIL PROTECTED] wrote:
Carlos,
What's the scoop on this release? Add my +1 to it, I see it's still in
your staging repo but
PING
Is this release missing PMC votes perhaps ? It still hasn't appeared on
repo1.
Thanks
Jorg
On Dec 6, 2007 12:25 PM, Mark Hobson [EMAIL PROTECTED] wrote:
I see this got released (thanks) but hasn't appeared on the central
repo, any reason for this?
Cheers,
Mark
On 30/11/2007,
On Nov 22, 2007 6:35 PM, Jason van Zyl [EMAIL PROTECTED] wrote:
I have two things to check:
- Make sure that when run in the context of Maven (the embedder) that
http proxying works
- Make sure that everything works offline well (I've removed the wiki
slurping as it proved to be entirely
Hi,
Any news on the release of this plugin ? Looking at [1] it seems that the
code was more than ready at the time ... and jira doesn't list anything
major either for 2.0-alpha-1. I'd say just get it out there and start
gathering real user feedback !
Regards
Jorg
[1]
Hi Raphaël,
On Nov 22, 2007 11:41 AM, Raphaël Piéroni [EMAIL PROTECTED] wrote:
There is currently a refactoring around the way archetypes are
known to the plugin and how they are deployed into repositories.
Thanks, do you have any threads I can look at to understand better what is
the
Stephane Nicoll wrote:
Hi,
I'd like to release maven-changes-plugin 2.0-beta-3. Significant fixes
are available in trunk and the latest release is almost one year old.
ping
Is this still on track to be released anytime soon ?
Thanks
jorg
Aaron Digulla wrote:
Since a few months, some European mirrors have become increasingly
unreliable. For example, maven.sateh.com is missing some packages which
were distributed in June, mirrors.dotsrc.org is missing some dated from
February (for example, asm/asm/3.0)!
Any particular reason
Jason van Zyl wrote:
Anyone have anything else? I'm not trying to consider everything that
Any chance that mvn could indicate the exact pom.xml locations of
duplicated projects ?
So instead of this:
[INFO] Project
Thierry Barnier wrote:
Hi Jaish,
I would recommend you the following maven proxies
-AbstractHorizon Proximity http://proximity.abstracthorizon.org/
-Apache Archiva http://maven.apache.org/archiva/
-Mergere Maestro http://www.mergere.com/
-Maven proxy http://maven-proxy.codehaus.org/
You left
Jason van Zyl wrote:
The tag is here:
http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.6/
Staging repository:
http://people.apache.org/~jvanzyl/staging-repository/maven-2.0.6/
And the distros you are interested in are here:
Jason van Zyl wrote:
Before I staged the release I just wanted to get some people to a build
first:
http://idisk.maven.org/jvanzyl/Public/maven/
Brian, Jason Dillon, and Dan Kulp have tried their builds and I just
wanted to get a little more feedback.
Cocoon and Excalibur trunk build
Eric Redmond wrote:
+1 for patching 2.0.6
I have yet to hear a single convincing argument for maintaining
broken behavior. Who cares if people depend on it being broken? Don't
upgrade. It's a defect, not a feature change. Pushing this to a major
version is way overkill.
+1
Jorg
Related:
The page
http://maven.apache.org/plugins/maven-release-plugin/examples/perform-release.html
looks messed up. In fact most of the pages for that plugin seem to
suffer from the same problem
Jorg
Julien HENRY wrote:
Hi,
On this page :
Jason van Zyl wrote:
Hi,
The assemblies that people are interested in are staged here:
http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/
Excalibur builds fine with this release, no apparent probs spotted.
Thanks,
Jorg
Jason Dillon wrote:
When I was building locally and on remote systems, I was using
-Dmaven.repo.local=repository to use a specific repository directoy.
But it looks like something inside of Maven or Surefire is not happy if
this value is not absolute or canonical. While most of Maven is
mraible wrote:
Here's the issue I discovered with 2.0.4 and JDK 6. AppFuse 2.x users have
reported other issues (i.e. plugins not firing) when using JDK 6.
http://jira.codehaus.org/browse/MNG-2709
http://article.gmane.org/gmane.text.xml.cocoon.devel/69786
It seems that maven builds a
Barrie Treloar wrote:
Overall for test results for maven-eclipse-plugin r472779
Tests run: 30, Failures: 0, Errors: 22, Skipped: 0
Some example warning messages:
[ maven embedder WARNING] repository metadata for: 'artifact
org.apache.maven.plugins:maven-eclipse-plugin' could not be
retrieved
Erik Drolshammer wrote:
Hi!
What is the difference between src/main/config and src/main/resources?
Anything you want to be included in the classpath of your application
should go in src/main/resources. Other config files that are not needed
at runtime by your application (eg
Hi,
The navigation on the top right and the last published date on the top
left are hardly readable with firefox/safari on Mac OS X (opera displays
it fine).
screenshot at http://www.domek.be/smalltext.png
Jorg
-
To
Hi Reinhard,
Reinhard Poetz wrote:
- install mod_proxy_html and load it within your Apache configuration
- add following lines to your Apache configuration file:
ProxyRequests Off
ProxyPass/ http://localhost:8082/
ProxyPassReverse / http://localhost:8082/
SetOutputFilter
Carlos Sanchez wrote:
I think this is already fixed for 1.1
Are you guys planning on releasing a first 1.1 snapshot anytime soon?
Jorg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
[ http://jira.codehaus.org/browse/MPIR-21?page=comments#action_55925 ]
Jorg Heymans commented on MPIR-21:
--
I just updated to 2.0.2 snapshot and
maven-site-plugin-2.0-20060106.225541-3.jar , the behaviour is still there.
no a href generated for archive
Type: Bug
Components: Inheritence and Interpolation
Versions: 2.0.1
Reporter: Jorg Heymans
A module in cocoon has following dependencies :
dependency
groupIdorg.apache.cocoon/groupId
artifactIdcocoon-core/artifactId
version2.2.0-SNAPSHOT/version
archetype creation broken
-
Key: ARCHETYPE-19
URL: http://jira.codehaus.org/browse/ARCHETYPE-19
Project: Maven Archetype
Type: Bug
Components: maven-archetype-plugin
Reporter: Jorg Heymans
Assigned to: Jason van Zyl
- when
fileset support
---
Key: ARCHETYPE-18
URL: http://jira.codehaus.org/browse/ARCHETYPE-18
Project: Maven Archetype
Type: Improvement
Components: maven-archetype-plugin
Reporter: Jorg Heymans
Assigned to: Jason van Zyl
it would be great
[ http://jira.codehaus.org/browse/MNG-1670?page=comments#action_51914 ]
Jorg Heymans commented on MNG-1670:
---
thinking about it, this effectively makes it impossible to have say
company-wide archetypes. I would like to up the priority of this but it seems
missing element does not trigger any warning
Key: MNG-1678
URL: http://jira.codehaus.org/browse/MNG-1678
Project: Maven 2
Type: Improvement
Versions: 2.0
Reporter: Jorg Heymans
spot the subtle error in below
[ http://jira.codehaus.org/browse/MNG-1656?page=comments#action_51752 ]
Jorg Heymans commented on MNG-1656:
---
I have verified with an SVN build as of a few minutes ago, the issue seems to
have been fixed.
xml-apis relocation wrong
cocoon.zones.apache.org 5.10 Generic_118844-08 i86pc i386
i86pc
Reporter: Jorg Heymans
Priority: Critical
Attachments: exception.log, parentpom.xml, pom.xml
doing package/install i get :
java.lang.StringIndexOutOfBoundsException: String index out of range: 1
using archetypes not deployed on central or one of it's mirrors
---
Key: MNG-1670
URL: http://jira.codehaus.org/browse/MNG-1670
Project: Maven 2
Type: New Feature
Versions: 2.0
Reporter: Jorg
[ http://jira.codehaus.org/browse/MNG-1670?page=comments#action_51834 ]
Jorg Heymans commented on MNG-1670:
---
http://jira.codehaus.org/browse/ARCHETYPE-1 seems like this was filed before.
using archetypes not deployed on central or one of it's mirrors
xml-apis relocation wrong
-
Key: MNG-1656
URL: http://jira.codehaus.org/browse/MNG-1656
Project: Maven 2
Type: Bug
Components: maven-artifact
Versions: 2.0
Reporter: Jorg Heymans
Priority: Critical
During my build, i get
[ http://jira.codehaus.org/browse/MNG-1656?page=comments#action_51657 ]
Jorg Heymans commented on MNG-1656:
---
http://jira.codehaus.org/browse/MEV-216 and
http://jira.codehaus.org/browse/MEV-222 are related
xml-apis relocation wrong
parent pom = child pom results in stack overflow error
--
Key: MNG-1644
URL: http://jira.codehaus.org/browse/MNG-1644
Project: Maven 2
Type: Improvement
Versions: 2.0
Reporter: Jorg Heymans
Though
-plugin
Reporter: Jorg Heymans
Even though i've specified pscp and plink in settings.xml, the deploy plugin
still seems to use scp , this is only the case for retrieving previous
metadata though, the deploy executes successfully otherwise.
[INFO] Retrieving previous metadata from [EMAIL
Reporter: Jorg Heymans
ideally, during deployment, the deployed pom should be stripped of elements
like build and distributionManagement
IRC log :
jorgCan someone enlighten me here : when i deploy an artifact (m2), why
does the deployed plugin contain the build
Versions: 2.0
Reporter: Jorg Heymans
The jar plugin automatically adds a pom.xml in META-INF, which makes sense. But
this pom.xml also contains local paths ie
build
sourceDirectoryd:\src\excalibur-trunk\framework\api\src\java/sourceDirectory
scriptSourceDirectorysrc/main
svn authentication fails during release:prepare
---
Key: MNG-1428
URL: http://jira.codehaus.org/browse/MNG-1428
Project: Maven 2
Type: Bug
Components: maven-release-plugin
Versions: 2.0
Reporter: Jorg
Versions: 2.0
Reporter: Jorg Heymans
I spent too much time trying to find out why maven wasn't accepting my scm urls
:
1) enter invalid scm url in pom
2) run maven release:prepare, it fails - release.properties is created
nevertheless
3) correct scm url in pom
4) rerun maven
[ http://jira.codehaus.org/browse/MNG-1276?page=comments#action_49889 ]
Jorg Heymans commented on MNG-1276:
---
minor nitpick - does not appear to be valid could be shortened to is
invalid
I don't know why you insist on the newlines here :
getLogger
duplicate project references
Key: MNG-1329
URL: http://jira.codehaus.org/browse/MNG-1329
Project: Maven 2
Type: Bug
Components: maven-eclipse-plugin
Versions: 2.0
Reporter: Jorg Heymans
eclipse:eclipse generates duplicate
direct support for mock classes
---
Key: MNG-1330
URL: http://jira.codehaus.org/browse/MNG-1330
Project: Maven 2
Type: New Feature
Versions: 2.0
Reporter: Jorg Heymans
a mockSourceDirectory element of some sort would allow
dealing with licenses
-
Key: MNG-1331
URL: http://jira.codehaus.org/browse/MNG-1331
Project: Maven 2
Type: New Feature
Versions: 2.0
Reporter: Jorg Heymans
Priority: Minor
maven could offer a configurable way to include project
Inheritance guid
Key: MNG-1315
URL: http://jira.codehaus.org/browse/MNG-1315
Project: Maven 2
Type: Improvement
Components: documentation
Versions: 2.0
Reporter: Jorg Heymans
Priority: Minor
It would be nice to have a guide on pom
[ http://jira.codehaus.org/browse/MNG-1276?page=comments#action_49221 ]
Jorg Heymans commented on MNG-1276:
---
I'ld be happy with a -DWarnInvalidPoms=false of some sort. Alternatively, you
could create a separate logging category for this and redirect
configured directory permissions ignored
Key: MNG-1282
URL: http://jira.codehaus.org/browse/MNG-1282
Project: Maven 2
Type: Bug
Components: maven-deploy-plugin
Versions: 2.0
Reporter: Jorg Heymans
I've
[ http://jira.codehaus.org/browse/MNG-1282?page=comments#action_49060 ]
Jorg Heymans commented on MNG-1282:
---
forgot to say : scp is used as provider
configured directory permissions ignored
Key: MNG
warning too verbose for invalid poms
Key: MNG-1276
URL: http://jira.codehaus.org/browse/MNG-1276
Project: Maven 2
Type: Improvement
Versions: 2.0
Reporter: Jorg Heymans
Basically , per module we get about 10-15
binary resources
Key: MNG-1234
URL: http://jira.codehaus.org/browse/MNG-1234
Project: Maven 2
Type: Bug
Components: maven-archetype-plugin
Versions: 2.0 (RC)
Environment: xp
Reporter: Jorg Heymans
As described here
http
73 matches
Mail list logo
