I took a quick look at the Maven-Nexus-plugin and there is an option to
disable it (skipNexusStagingDeployMojo), so I would start there.
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
they turn on the maven-flatten-plugin and a publish plugin.
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
On Mon
nheritance. It also makes it easier with dependency management,
the reasoning about which import takes preference with an inherited parent
import is really hard to understand.
Take a look at it, and maybe it will solve your problem.
Nick Stolwijk
~~~ Try to leave this world a little better than
artifacts,
so there is no need to publish your parent pom.
Maybe this is the solution you are looking for.
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time
Test
com.fasterxml.jackson
jackson-bom
2.13.5
pom
import
[1] https://www.baeldung.com/spring-maven-bom
Nick Stolwijk
~~~ Try to leave this world a little
h you a better build in the future and if you need any help with that,
please let me know.
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but
://www.mojohaus.org/extra-enforcer-rules/banDuplicateClasses.html
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
On Sat
I see there is one little mistake in that blogpost.
You should add the original dependency with provided to
prevent it from entering the classpath, or else you still end up with both
dependencies on your classpath.
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found
rsion of the artifact once to the
repository" way, but that depends on how much control you have over your
repository.
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted
to your own artifact repository and start using
that version in your project.
It all depends on how long you are expecting to support the solution.
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling
of the BBED.
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
On Sat, 29 Jul 2023 at 00:33, wrote:
> I think
-lang
2.6
${project.build.outputDirectory}
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have
nd fix any violation
with an clause.
And, of course, try to push your change upstream as soon as possible, so
you don't have to maintain this dependency hell forever.
Hth,
[1] https://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html
Nick Stolwijk
~~~ Try to leave this world a li
tart about the runtime. If you have
duplicate classes and Maven "behaves", who says that the runtime behaves in
the same way?
I would make it a bigger issue that you have duplicate classes, instead of
trying to live with those duplicates.
With regards,
Nick Stolwijk
~~~ Try to leave this w
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
On Fri, 28 Jul 2023 at 21:25, wrote:
> I already as
You are right, I forgot that that still exists. :-S I do think that that
way of dependency management is highly discouraged and IMNSHO should be
discarded in your build as a first step.
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn
provided by Maven Central instead of artifacts built internally?
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord
.
Are wildcard / bom resolution a good idea for the includes? Wildcard looks
a lot simpler to implement.
Examples:
software.amazon.awssdk:bom
software.amazon.awssdk:*
What do you think?
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes
.
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
On Thu, Sep 2, 2021 at 5:41 PM Mantas Gridinas wrote
Hi,
I think you need to fix the parameter resolution: ${depStagingArea/pcs}
should be ${depStagingArea}/pcs
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your
d for that Maven version and activated profiles
[1] https://github.com/jcgay/buildplan-maven-plugin
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time bu
'
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
On Mon, May 3, 2021 at 9:50 PM Nick Stolwijk
wrote
D SUCCESS
[INFO]
[INFO] Total time: 1.917 s
[INFO] Finished at: 2021-05-03T21:47:34+02:00
So why is the new SNAPSHOT of the Maven Dependency Tree checking
dependencies that are not in the dependency tree?
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better
lugins.dependency.tree.TreeMojo.execute
(TreeMojo.java:276)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy
Hi Enrico,
I did a search and replace on our domain name. The Nexus instance at our
company is a mirror for Maven Central.
And it is the only repository used in the build. See the output for
list-repositories in the last mail.
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better
Hi Enrico,
It looks like it is trying to update the world while using repositories I
can't explain. ;-)
[INFO] --- maven-dependency-plugin:3.1.4-SNAPSHOT:list-repositories
(default-cli) @ commons-lang ---
Downloading from public_nx3:
[INFO]
[INFO] Total time: 31:47 min
[INFO] Finished at: 2021-05-03T12:51:06+02:00
[INFO]
[1] https://issues.apache.org/jira/browse/MDEP-644
With regards,
Nick Stolwijk
~~~ Try to
To update the BOM dependencies you can use the Maven versions plugin:
mvn versions:use-latest-versions versions:update-properties
-DgenerateBackupPoms=false
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy
[2] https://github.com/jonathanlermitage/oga-maven-plugin
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden
Hi Anton,
I have taken a look at the issues fixed in 3.0.1 and I think you'll find
the information you need in MDEP-409[1].
[1] https://issues.apache.org/jira/browse/MDEP-409
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes
plugin (alas, they didn't
support Tycho either) and are now migrating to the aforementioned plugin.
[1]
https://www.eclipse.org/tycho/sitedocs/tycho-release/tycho-versions-plugin/set-version-mojo.html
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found
/exec/InvokerMavenExecutor.java#L318
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
On Mon, Nov
, but I didn't find an
example of a toolchain with Maven itself.
Can anyone enlighten me?
[1] https://github.com/aleksandr-m/gitflow-maven-plugin
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling
As far as I know you should use use-latest-versions, which does checks if
you use the latest version of the imported pom and not the latest versions
of the imported dependencies.
With regard,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes
I had the same issue a while back [1]. We now use use-latest-versions and
no longer use properties for versions most of the time.
Hth,
[1] https://www.mail-archive.com/users@maven.apache.org/msg142064.html
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
future conflicts. It’s still good practice to regularly check for and
update to the latest versions.
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time
That was not a workaround, but me trying to reproduce the problem. I wasn't
able to reproduce it.
All the artifacts in the reactor could be found without building them. Are
you maybe trying to only build one module instead of the reactor?
With regards,
Nick Stolwijk
~~~ Try to leave this world
The verbose flag was removed in newer versions of the plugin. You could try
an old pluginversion:
mvn org.apache.maven.plugins:maven-dependency-plugin:2.10:tree -Dverbose
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die
. Check local repository, nothing of my project is there.
My output shows SNAPSHOT dependencies inside my project.
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted
Put the testutils and the tests in the same project as foo in src/test/java
and make the tests package private (JUnit Jupiter). Other projects can
depend on the test artifact of foo and only use the test-utils.
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found
-maven-plugin/issues/346
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
try to
escape them?
[1] https://github.com/nickstolwijk/MavenPropReplacement.git
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done
or in any of the parent poms of
your project.
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
On Wed, Jan 15
Hi folks,
Has anyone tried to publish the site generated by Maven as a docker image?
Are there examples of such a setup?
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
her types of projects. It is only
unfortunately so, that the ASF and Apache HTTP server are both called
'apache'.
With regards,
Nick Stolwijk
[1] https://projects.apache.org/projects.html
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy i
plugins/maven-dependency-plugin/tree-mojo.html#verbose
[2] http://maven.apache.org/shared/maven-dependency-tree/
> I would also take your approach of "a dependency management pom" (BOM,
bill of materials) to control transitive dependencies.
Yeah, it seems that would be the best option.
Wi
management?
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
sing this flag.
[1] https://github.com/mojohaus/versions-maven-plugin/issues/291
[2] https://github.com/mojohaus/versions-maven-plugin/issues/267
With regards
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in fee
Hello,
I found this old mail about running test multiple times with different
JDK's.
Has there been any work done to make this possible? Or is the best possible
solution to use the CI server to run multiple runs with different JDK's,
perhaps using toolchain.
With regards,
Nick Stolwijk
If that's the case then maybe take a look at the analyze-dep-mgt goal of
the dependency plugin.[1]
Hth,
Nick Stolwijk
[1]
https://maven.apache.org/plugins/maven-dependency-plugin/analyze-dep-mgt-mojo.html
~~~ Try to leave this world a little better than you found it and, when
your turn comes
Hi,
I was wondering why the parameter processDependencyManagementTransitive is
available on the dependency-updates-report goal[1] of the Versions Maven
Plugin but isn't available on its counter-part display-dependency-updates
[2]
?
With regards,
Nick Stolwijk
[1]
https://www.mojohaus.org
You can add the properties tag directly under the root element ()
of your POM[1] file.
1.
2. 1.8
3. 1.8
4.
[1] Project Object Model
The default source level is still at 1.5, due to backward compatibility
issues.
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better
You can ban duplicate classes with the enforcer plugin [1].
[1] http://www.mojohaus.org/extra-enforcer-rules/banDuplicateClasses.html
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate
.)
Would implementing this be an addition to the dependencies plugin?
(crossing fingers, I guess this is done in Maven itself and not in a
plugin).
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any
d of the
JRE bin directory.
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
-maven-plugin/display-property-updates-mojo.html
scans
a projectand produces a report of those properties which are used to
control artifact versions and which properies have newer versions available.
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
thinking of a Bash or Groovy script to parse the aggregator pom to
build up the --project-list argument.
Does anyone see an easier way?
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling
://www.maestrodev.com/better-build-maven
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
You can use the dependency:tree[1] goal to view a tree of your
dependencies to see if the correct version of Log4J is being included
in the compiler classpath.
[1] https://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html
Hth,
Nick Stolwijk
~~~ Try to leave this world a little
-1.2.17.jar
5af35056b4d257e4b64b9e8069c0746e8b08629f log4j-1.2.17.jar
02:28:47 ~/.m2/repository/log4j/log4j/1.2.17$ cat log4j-1.2.17.jar.sha1
5af35056b4d257e4b64b9e8069c0746e8b08629f
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and,
when your turn comes to die
if [ $? -eq 0 ]; then
echo $jar
fi
done
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and,
when your turn comes to die, you can die happy in feeling that at any
rate you have not wasted your time but have done your best ~~~
Lord Baden-Powell
On Wed, Apr 30, 2014
includes
include**/*Builder.class/include
/includes
/configuration
/execution
/executions
/plugin
With regards,
Nick Stolwijk
~~~ Try
That's called a transitive dependency and this blog[1] explains nicely why
you shouldn't use those.
[1] http://uglycoder.blogspot.nl/2008/04/flaw-with-mavens-transitive.html
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you
the same
error as your colleague.
Hth,
Nick Stolwijk
On Thu, Nov 28, 2013 at 3:32 PM, Tommy Svensson to...@natusoft.se wrote:
parent
groupIdxxx.xxx.xxx/groupId
artifactIdxxx-shared/artifactId
version2.0.26-SNAPSHOT/version
/parent
Maybe it is mustard after the mail (as the Dutch call it. ;) ), but here is
a nice article about the standard directory layout of Maven:
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better
dependency tree, but with
different groupId's. Maven will think those are different jar files. Check
your dependency tree with mvn dependency:tree to see where those
dependencies come from.
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes
-dependency-plugin/analyze-dep-mgt-mojo.html
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
On Sat, May 4, 2013
) Check in
Voila, stable label and ready for next release.
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
Or take a look at the Maven Release Plugin - branch goal [1] and it's
documentation page [2].
[1]
http://maven.apache.org/maven-release/maven-release-plugin/branch-mojo.html
[2]
http://maven.apache.org/maven-release/maven-release-plugin/examples/branch.html
Hth,
Nick Stolwijk
~~~ Try to leave
Hi,
Did you try ${settings.localRepository} because the property is a settings
property?
Why your second example works seems evident. You set the property, so you
can read it.
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die
-resources-plugin.
[1] http://repo1.maven.org/maven2/org/apache/apache/9/apache-9.pom
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and,
when your turn comes to die, you can die happy in feeling that at any
rate you have not wasted your time but have done your
is not
dependend on your '~' shortcut?
Hth,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and,
when your turn comes to die, you can die happy in feeling that at any
rate you have not wasted your time but have done your best ~~~
Lord Baden-Powell
On Mon, Feb 6, 2012 at 4
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Thu, Jun 23, 2011 at 3:44 PM, Rick Mangi rick.ma...@mtvn.com wrote:
Hello Maven Users,
I'm trying to migrate my users to a new nexus repository on a different
If you want multiple wars I think you are better of deploying an ear file.[1]
[1] http://maven.apache.org/plugins/maven-ear-plugin/
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Thu, Jun 23, 2011 at 5:05
The name in your target directory is defined by the finalName in your
build section[1].
[1] http://maven.apache.org/pom.html#Build_Settings
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Thu, Jun 23, 2011
I guess you could make an aggregator pom in your trunk/ which kicks of
all 3 builds. If you branch this pom it would succeed.
Or you could move your parent pom one level higher and let it serve as
parent and aggregator pom.
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM
Your request doesn't make any sense to me. Could you please describe
what you want to accomplish?
With regards,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Tue, May 24, 2011 at 1:42 PM, Brosh, Yossi yossi.br
/
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Tue, May 24, 2011 at 2:23 PM, Brosh, Yossi yossi.br...@sap.com wrote:
I need to install : maven-deploy-plugin , in order to run maven deploy
Best regards
[2] http://mojo.codehaus.org/mail-lists.html
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Tue, Mar 29, 2011 at 11:47 PM, Dave DaveLists dbfli...@gmail.com wrote:
Hello,
New to the group here.
First
Try mvn help:effective-settings to see your settings as maven sees
them. Are you sure your server id is the same as your
repository/mirror id?
With regards,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Thu
I don't know whether this is fixed in newer versions of the Antrun
plugin, but I noticed you use version 1.3, while version 1.6 is also
available. You can give it a try and hopes it fixes your problem.
With regards,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Thu, Mar 10, 2011 at 4:49 PM, Pulkit Singhal pulkitsing...@gmail.com wrote:
Hello Everyone,
I'm following the instructions given here to create a new maven plugin
Does it need to be on the classpath of surefire or of your unittests?
If it is the first you are on the good way. You can check with -X what
the classpath for surefire is.
For the second, add a normal dependency with scope test.
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
for it.
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Thu, Mar 10, 2011 at 9:22 PM, Dipl.-Ing. Torsten Liermann
l...@liermann-it.de wrote:
Thanks Nick.
I need the artifact in the runtime classpath for the unit
First, this message belongs to the user list, so redirecting there.
For your question, take a look at SCM for Subversion[1].
[1] http://maven.apache.org/scm/subversion.html
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I
Take a look at the Advanced Artifact-Matching in includes and
excludes on the advanced descriptor page[1].
[1]
http://maven.apache.org/plugins/maven-assembly-plugin/advanced-descriptor-topics.html
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
I just checked our 1.8.0.1 instance of Nexus and it is right there
under the configuration of a hosted repository:
Deployment policy:
Allow redeploy
Disallow redeploy
Read only
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I
I've also checked 1.3.6 (still in production here, Saturday we are
moving to 1.8.0.1) and, indeed, it isn't there. You have to upgrade to
a newer version to have it. It isn't a Pro feature, the free version
also has it.
With regards,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
We just did a reinstall on a new server and planning to copy the
repositories by hand and do a reindex. We had a testrun and it went
painlessly. The mirror and snapshot repositories we just deleted, as
to do some cleanup.
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM
Yes, we had to upgrade Jira, Hudson, Nexus and Sonar, so we just copy
the data and replace the (virtual) machine. That way, when the upgrade
goes wrong, we can easily go back to the old situation.
With regards,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23
,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Wed, Jan 5, 2011 at 6:58 PM, Thiessen, Todd (Todd)
tthies...@avaya.com wrote:
Configure your Nexus server to not allow artifacts to get overwritten. You
can't stop
What goals are you running? The site lifecycle doesn't take
build/pluginManagement into account and you have to set the version in
/project/reporting/plugins/
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
Unfortunately not.[1]
[1] http://maven.apache.org/pom.html#Reporting
With regards,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Tue, Jan 4, 2011 at 3:29 PM, Leon Rosenberg rosenberg.l...@gmail.com wrote
central, hosted snapshots with cleanup policy, hosted releases with
deploy once policy, hosted thirdparty repository. All cleanly
seperated and easily backupped.
For staging builds you would need Nexus Professional, for all your
other wishes the normal Nexus fits like a glove.
Hth,
Nick Stolwijk
If you still have the same snippet in your pom, you only have the
snapshotRepository and not the normal repository element.
With regards,
Nick Stolwijk
~Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Wed, Dec 8, 2010 at 5:44 PM
/snapshotRepository
/distributionManagement
And create the inhouse and inhouse-snapshot repositories inside nexus
and add them to the right groups.
With regards,
Nick Stolwijk
~Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
I can't answer your question, sorry. Maybe you should post this at the
dev list. There resides the most people with intimate knowledge about
Maven's plugin setup.
With regards,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl
On Sat, Dec 4
Although this is highly seen as a bad practice, you may want to start
by looking here:
http://docs.codehaus.org/display/MAVENUSER/FAQs-1#FAQs-1-Isitpossibletocreatemyowndirectorystructure%3F
More information about the pom structure:
http://maven.apache.org/pom.html
Hth,
Nick Stolwijk
~Java
Yes, just bind the javadoc:jar goal twice with different configuration.
With regards,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl
On Thu, Nov 11, 2010 at 8:35 PM, Gerard Weatherby
gerard.weathe...@gmail.com wrote:
Is there a way
I would suggest you use Maven(+Hudson)+Sonar.
Maven for building and gathering information
Hudson for CI (but it can be left out)
Sonar for reporting
Sonar can do nice reports for coverage, unit tests, QA metrics, etc.
Hth,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS
1 - 100 of 523 matches
Mail list logo
