+1.
On 06/11/2013 3:57 PM, Wayne Fay wrote:
I want to know Should I just deploy my entire WEB-INF/lib to Artifactory?
Most likely, no, you should not do this.
Instead spend the time to match each Jar file up to an equivalent Jar
file deployed in Central. For Jars which do not exist in Central
Hello,
say I have a parent pom, which defines:
org.apache.maven.plugins
maven-surefire-report-plugin
2.16
report
I now do not want
> I want to know Should I just deploy my entire WEB-INF/lib to Artifactory?
Most likely, no, you should not do this.
Instead spend the time to match each Jar file up to an equivalent Jar
file deployed in Central. For Jars which do not exist in Central or
those with modified contents, you can cons
On 06/11/2013 2:46 PM, Manfred Moser wrote:
Imho you should not just upload all the jars. Instead find out the exact
version of what they are by doing a shasum of the jars and use the
checksum search in Nexus or on Central to identify the jars.
http://search.maven.org/#advancedsearch%7Cgav
Only
It's currently not set here.
It sounds like I need to set this, and then enforce with a pre-commit hook.
Since this will be a large undertaking (I imagine the internal SVN
server has the same default settings as my local one), I'll encourage
people to use PowerShell until the repository is cle
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
14:51:
28+0100)
Maven home: D:\apache-maven-3.0.5\bin\..
Java version: 1.7.0_45, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_45\jre
Default locale: nl_NL, platform encoding: Cp1252
OS name: "window
Imho you should not just upload all the jars. Instead find out the exact
version of what they are by doing a shasum of the jars and use the
checksum search in Nexus or on Central to identify the jars.
http://search.maven.org/#advancedsearch%7Cgav
Only upload the ones you can not identify.. and ev
Agreed, there must be a better explanation.
I'm open to it.
What is your environment like?
My environment is listed in the original message. Perhaps there is a
clue in environment differences?
Mark
/mde/
On 11/6/2013 11:35 AM, Robert Scholte wrote:
Well, I'm a Windows user and have done a
Well, I'm a Windows user and have done a lot of releases with svn.
There must be a better explanation.
Robert
Op Wed, 06 Nov 2013 17:40:09 +0100 schreef Mark Eggers
:
Train wreck of debugging output below.
Sorry for the line wrap.
For those of you interested in just the answer, the appare
I am trying to figure out the best way to migrate over and use Maven for
Dependency Management.
My question is : I have about 130 Jars in the Project we are a large
project. I have Artifactory set up. SOme of the JARs I don't even have
versions for as they have been around for years. A few we ha
Train wreck of debugging output below.
Sorry for the line wrap.
For those of you interested in just the answer, the apparent work-around
is to use PowerShell on Windows.
On 11/5/2013 2:16 PM, Robert Scholte wrote:
Hi,
If you run Maven with debug logging (add -X to the arguments) you will
se
> But on my friend's machine, Maven complained during compilation that it
> could not find the Java file. By moving the file into a directory structure
> matching its stated package, we got "mvn compile" and "mvn test" to work on
> his machine as well. I'm curious why our "mvn compile"s are behavin
I think you have some typos in your e-mail
my.namesapce.test should be org.mynamespace.test to match
src/test/java/org/namespace/test/
Give the commands that you used to compile on each machine and the
output log
You might check in your settings.xml files on each machine to make sure
that t
They should work with WAS 8.5.5.x.
Here's the IBM site with the links:
https://www.ibmdw.net/wasdev/downloads/websphere-application-server-developer-tools-v8-5-5/
/Anders
On Wed, Nov 6, 2013 at 3:28 PM, wrote:
> Exactly those you sent me the URL. I haven't seen yet. Hopefully they work
> with
Unless you have configured the maven-compiler-plugin to use a compiler
other than the default, the JDK's javac is used. So I would assume it's due
to Apple's JDK accepting this mismatch while Oracle's JDK doesn't.
/Anders
On Wed, Nov 6, 2013 at 3:47 PM, Andrew Pennebaker wrote:
> On my machine,
On my machine, I have a Java file with a different stated package name (
my.namespace.test) than the file's directory structure would indicate (
src/test/java/org/namespace/test/). On my machine, "mvn compile" and "mvn
test" still work without issue or warning.
But on my friend's machine, Maven co
Why are you doing all of this?
What are you building that is so far outside the normal way to build
EARs that it requires that you do this?
Why do you need hibernate to compile but not to run?
If hibernate is being provided at run-time then scope "provided" should
handle this properly.
I may
Exactly those you sent me the URL. I haven't seen yet. Hopefully they work
with WAS 8.5.5.0! As far as I know, 8.5.5.1 shall be available on November
11 only! I just searched for an update with the Installation Manager, but
nothing seams to be available.
I'll try in any case now. Thanks for the
What WAS plugin for Eclipse are you talking about. The ones in Eclipse
marketplace should work with Kepler SR1 (v4.3.1) according to the info
there [1] [2]. They were just recently updated (Nov 1).
[1]
https://marketplace.eclipse.org/content/ibm-websphere-application-server-v855-developer-tools-ec
Try to define a filter, similar to the following snippet:
lib
true
true
true
src/main/resources/
**/*application.xml,**/*MANIFEST.MF
The outcome of the announced tests are:
On working with eclipse Kepler, not having any WAS-Plugin installed the
classes compiled by maven, either started from command line or through
m2e-wtp are correct, the resulting ear can be deployed on the WebSphere
App-Server and runs without error!
I ho
Bonsoir,
The Mojo team is pleased to announce the release of the Webstart
Maven Plugin version 1.0-beta-4
The Webstart Maven Plugin generates application bundles that can be
deployed via Web Start. The plugin can be used to prepare standalone
Web Start applications or Web Start applications bundl
I have a plugin that needs to access just one dependency from the project.
Currently I use "@requiresDependencyResolution compile" and build the
entire classpath:
https://github.com/JodaOrg/joda-beans-maven-plugin/blob/master/src/main/java/org/joda/beans/maven/AbstractJodaBeansMojo.java#L213
This
Why do you need the Class-Path entry for an ear? JEE containers have other
means to create the classpath.
/Anders
On Wed, Nov 6, 2013 at 9:54 AM, Surendran D wrote:
> Hi,
> I am currently building and EAR file using maven-ear-plugin
>
> I have a requirement to exclude some of the Class-Path: e
Hi,
I am currently building and EAR file using maven-ear-plugin
I have a requirement to exclude some of the Class-Path: entries from
MANIFEST.MF file.
For example I have 3 dependencies hibernate-core.jar, quartz-1.6.5.jar and
poi-3.7.jar in my class path (in my dependency of pom.xml)
When I buil
To whom it may concern, https://github.com/code54/buildversion-plugin
provides exactly the desired logic.
One caveat exists, which is that pushing tags for past commits will
decrease the revision numer in subsequent builds. But if one sticks to
the maven-release-plugin for tagging, everything
Hi,
this is much better.
Based on my actual knowledge, yes I believe it must have a relation with
the Juno Version of eclipse, but I don't know how and why.
The differences between the two flavors of project are minimal and due to
the differences of App-Server and Databases used. If Java would
27 matches
Mail list logo
