Maybe I'm missing something, but there seems to be a hole in the logic
of the rpm-maven-plugin mappings, and
the way file permissions are created.
Looking at the official documentation,
http://www.mojohaus.org/rpm-maven-plugin/map-params.html, I see
filemode(*recommended*)
This is UNIX
${project.groupId}
${rpm.name}
${project.version}-${rpm.release}
noarch
rpm
On 12/07/2015 02:55 PM, Steve Cohen wrote:
Actually, I found a way. If I am willing to let my "short name" become
the archiveId, (and thus live with the rpms in a
ate naming
schema to find artifacts / versions etc. If you change that the whole
system will not work at all..
So the name which is stored within a maven repository can't be changed.
Kind regards
Karl Heinz Marbaise
On 12/7/15 7:44 PM, Steve Cohen wrote:
Our organization has a convention
Our organization has a convention for naming rpms. Typically, the rpm
will have a shorter base name than the Maven project. There is also a
convention around how releases are named. So we want a name
like|${shortname}-${project.version}-${release}.noarch.rpm|.
I want to build such rpms using t
of
Maven, it seemed wrong and I have verified that it is.
It's probably a typo, one that has confused some people, for example, on
Stack Overflow:
http://stackoverflow.com/questions/17516313/possible-bug-when-parsing-properties-with-goal-regex-property-of-build-helper
Can someone fix it?
Steve Cohen
What with the Codehaus "termination of Maven services" and other recent
developments, what has happened to the handy list of predefined project
properties and other properties that was once but no longer is available
from http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide ?
I need
e you want to use in the
attach task...
(and since you will always be moving, you have the added bonus of knowing
that its a fresh file as the old ones will always have been moved away)
On 9 April 2015 at 21:47, Steve Cohen wrote:
On 04/09/2015 03:04 PM, Stephen Connolly wrote:
On Thursday,
On 04/09/2015 03:04 PM, Stephen Connolly wrote:
On Thursday, April 9, 2015, Steve Cohen wrote:
I think that both of these solutions (Karl's and Stephen's) fall short
because the redline:rpm ant task does some opaque magic to name the rpm.
Therefore it is impossible to specify oth
l 9, 2015, Karl Heinz Marbaise wrote:
Hi Steve,
simplest solution would be to use buildhelper-maven-plugin to attach the
artifact and it will be deployed to a repository...
Kind regards
Karl Heinz Marbaise
On 4/9/15 3:57 PM, Steve Cohen wrote:
Thanks for this tip, Mark. It meets the need even th
I expect that with Luna, this will go away.
On 04/08/2015 02:06 PM, Steve Cohen wrote:
I probably left out the most important part of this log fragment. I
didn't immediately realize its relevance.
12:37:43.523 [main] DEBUG Sisu - Add publisher:
com.google.inject.internal.Injec
Thanks for this tip, Mark. It meets the need even though it is a bit
rough around the edges, the need to involve ant at this point, etc.
One question I have: is there a way to have the rpm that gets built
installed into the repo, deployed, etc. As it stands now, only the
intermediate archives
and line Maven does not
have this stuff in it. But I fail to see how something installed in
Eclipse would have this effect.
On 04/08/2015 11:36 AM, Steve Cohen wrote:
I finally got around to making the warnings about slf4j static logger
disappear from my Eclipse builds and now I get this, inst
What's an MCVE?
On 04/08/2015 11:45 AM, Curtis Rueden wrote:
Hi Steve,
I don't see that stuff with my builds. Post an MCVE somewhere.
-Curtis
On Wed, Apr 8, 2015 at 11:36 AM, Steve Cohen wrote:
I finally got around to making the warnings about slf4j static logger
disappear from
I finally got around to making the warnings about slf4j static logger
disappear from my Eclipse builds and now I get this, instead with every
build step Maven executes?
-[explicit
bindings]---
0. ProviderInstanceBinding{key=Key[type=c
I finally got around to making the warnings about slf4j static logger
disappear from my Eclipse builds and now I get this, instead:
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: u
I'm trying to run the rpm plugin on an old solaris box that is running
rpm v3.0.4, and the plugin complains that it can't find rpmbuild. IIRC,
rpmbuild was added to the rpm suite maybe 10 years ago and this is older
than that. Is that supported by the plugin and if so, how?
-
new work. Old
applications will need to be ported. There's no way around it.
Thanks to everyone for trying.
Steve Cohen
On 04/02/2015 10:35 AM, sco...@javactivity.org wrote:
Thanks for your reply, Stephen.
"On a hiding to nothing" - that's not an expression I'm famil
quot;maven user” and not a
"maven developer” - I personally don’t like enhancing other tools unless there’s an
easy way for me to contribute that fix back and get it into the main build.
Just my 2 cents advice.
- JK
On Apr 1, 2015, at 9:48 AM, Steve Cohen wrote:
That sounds like it mi
That sounds like it might be a possibility. But after looking at it, my
initial take (which is quite possibly wrong!!) is that it might be
easier to extend the compiler plugin, and the jar plugin, to use the
vpath. Basically, you're just writing a new SourceInclusionScanner.
This seems like i
would want all the rest of the maven compiler plugin to be executed.
I have never created a plugin before. How difficult, or doable, is it
to "extend" a plugin in this way? Can someone point to an example where
such an extension has been done?
Thanks.
On 03/31/2015 05:07 PM, S
Please disregard my previous message. I inadvertently pressed "send"
before it was finished. Sorry.
On 04/01/2015 08:43 AM, Steve Cohen wrote:
On 03/31/2015 05:07 PM, Steve Cohen wrote:
Okay, I am thinking that this could be best done by writing a custom
plugin. This plugin would
On 03/31/2015 05:07 PM, Steve Cohen wrote:
Okay, I am thinking that this could be best done by writing a custom
plugin. This plugin would walk down the VPATH, capturing the names of
all the java files to be compiled, under each element in the VPATH, and
pruning the list according to the VPATH
e
On Tue, Mar 31, 2015 at 11:25 AM, Steve Cohen
wrote:
I work for an organization which uses an SCM/Build process based on the
following:
SCM: a ancient legacy horror of a system
Build: Alcatel-Lucent nmake
With this system the organization maintains a large suite of
applications. The system i
ustom environment variables, different jvms, etc. etc. It can
run any number of utilities via shell scripts, Maven, Ant, Gradle, etc. etc.
That might be a more fruitful place to start.
Cody Fyler
Lending Grid Build Team
G=Lending Grid Builds
(515) – 441 - 0814
-Original Message-
From: Steve
I work for an organization which uses an SCM/Build process based on the
following:
SCM: a ancient legacy horror of a system
Build: Alcatel-Lucent nmake
With this system the organization maintains a large suite of
applications. The system is monstrously inflexible and a pain to work
with. T
There is no bug here. I was mistaken. I inadvertently neglected to
convert one of the MQ jars to system scope and so it still appeared in
the manifest. System scope jars are NOT included in the manifest which
is the correct behavior.
Sorry for the confusion.
On 07/28/2014 09:43 AM, Steve
I don't think so. The path that must be provided with system scope is a
feature I very much want. I chose system over provided for this reason.
On 07/28/2014 12:14 PM, Ron Wheeler wrote:
Scope - "provided" might do the job.
On 28/07/2014 12:52 PM, Steve Cohen wrote:
Act
I'm now being told by IBM that they provide OSGI-compliant jars which
may make all this moot.
On 07/28/2014 12:14 PM, Ron Wheeler wrote:
Scope - "provided" might do the job.
On 28/07/2014 12:52 PM, Steve Cohen wrote:
Actually, given my requirements, I think scope system is
es that are supposed to be put in the
JVM's ext directory or equivalent.
You do not want to use system
On 28 July 2014 15:43, Steve Cohen wrote:
Sadly, my hopes were not completely fulfilled.
In spite of specifying the MQ jars as system dependencies with their own
paths, the maven manifest
specify the classpath on the command line.
Doable, but annoying.
This is arguably a bug. If system dependencies are required to list
their path, should not the manifest classpath generator respect these?
On 07/28/2014 09:13 AM, Steve Cohen wrote:
I think the most painless and maven-like way to
non-standard location.
Then, I'm hoping that the manifest generator of the application jar will
pick up these locations and put them on the classpath.
On 07/25/2014 01:05 PM, Steve Cohen wrote:
Yecch. I'm already using the assembly plugin. But it appears that with
that approach
Yecch. I'm already using the assembly plugin. But it appears that with
that approach instead of using the lovely dependency set, I must use
s (handle each jar individually) because this is the highest level
that allows renaming of the files.
Ugh.
On 07/25/2014 12:44 PM, Steve Cohen
/www.javassist.org/) to "fix" IBM's limited logic?
Regards,
Curtis
On Fri, Jul 25, 2014 at 12:07 PM, Steve Cohen
wrote:
To elaborate further on what I'd like to do, I think I need to create a
POM file that simply lists all these jars and supply that to the Nexus
archive upload
ng of these files.
On 07/25/2014 11:50 AM, Steve Cohen wrote:
Container? Guess I need to supply more details.
This is a standalone J2SE app. The server side is legacy. There is no
container. it isn't a web app.
Instead it's run as a jar with the classpath generated from maven'
al" jars are in front of everything else on the classpath.
On Fri, Jul 25, 2014 at 9:07 AM, Steve Cohen wrote:
I have a client application that was developed with Websphere MQ. Our
company has a Maven nexus repository. In this repository, we have a place
to store third party jars.
IBM named them in their release. So we have to
repackage the application so as to accomplish this.
Before I jump into hacking this mess into place, is there a recommended
way of handling this so that the maven repository, maven, and ibm are
all happy?
Thanks,
Steve Cohen
51 PM, Russell Gold wrote:
Bringing in the source should be a function of your editor. What are you using?
It works fine for me in IntelliJ
- Russ
On Nov 5, 2013, at 6:09 PM, Steve Cohen wrote:
On 11/05/2013 04:22 PM, Olivier Lamy wrote:
Use mvnDebug cli instead of mvn
--
Olivier
On Nov 6,
On 11/05/2013 04:22 PM, Olivier Lamy wrote:
Use mvnDebug cli instead of mvn
--
Olivier
On Nov 6, 2013 8:09 AM, "Steve Cohen" wrote:
I have a need to debug the maven-assembly-plugin which is not functioning
correctly. I have found the instructions for setting up a debugging
envir
I have a need to debug the maven-assembly-plugin which is not
functioning correctly. I have found the instructions for setting up a
debugging environment for maven itself within eclipse.
What is the best way to get the source for this plugin so that it can be
used by the debugging process. I
I have a bug on the Codehaus jira for the maven assembly plugin
(http://jira.codehaus.org/browse/MASSEMBLY). Although I have configured
my account to notify me by email on any changes on my bugs, whether from
myself or anyone else, I never get any emails. I have written to the
contacts listed
When building a .tar.gz archive with the maven assembly plugin, should
it not be keeping the timestamps of the files it is adding to the
archive? This is how tar behaves. I find it NOT to be the case with
the assembly plugin. The files are dated with the time they were added
to the archive.
When creating an assembly, I would like the timestamps of each file
stored within the archive to be the same as those on the files being
assembled. Is this possible
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
On 10/10/2013 05:35 AM, Martin Gainty wrote:
MG>Please file a bug in JIRA
MG>http://jira.codehaus.org/browse/MASSEMBLY
done.
http://jira.codehaus.org/browse/MASSEMBLY-666
also enhancement requests:
http://jira.codehaus.org/browse/MASSEMBLY-667
http://jira.codehaus.org/browse/MASSEMBLY-668
---
I have found the following.
Given an assembly descriptor that produces an .tar.gz archive,
if more than one fileset provides content feeding into the same output
directory, the archiver does not create a folder entry in the archive.
This means that there is nothing to apply a to, and when
the
It does not. I hadn't tried using '/' as the output directory spec
(i.e. the base-directory) but it doesn't help. The basic problem is this:
The archiver does not create an entry in the archive for the
base-directory. This is because no matter where you put the
it applies to directories WI
Martin, yes, I'm well aware of that functionality.
However, I cannot figure out how to apply it to the base directory.
Let's say I've set all my filesets which are packaged underneath the
base directory to
775
664
The plugin handles this beautifully.
But let's suppose I want the basedir of th
On 10/09/2013 11:43 AM, Baptiste Mathus wrote:
What are you trying to do? The 'why' may also help.
Is there a way to do this?
--**--**-
To unsubscribe, e-mail:
users-unsubscribe@maven.**apache.org
For additional commands, e-mail: us
Is there a way to do this?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Why isn't there a way to set the ownership of files packaged by the
assembly plugin, similar to how it allows you to set permissions?
The unix tar program offers --user= and --group=. Is there any way
to do this in the assembly plugin?
---
I have noticed the following behavior that seems strange to me.
I am using the assembly plugin to create a tar.gz archive. I have
several filesets that I use, and they all specify file and directory
permissions. Some filesets create a single target directory from a
single source directory an
On 01/09/2013 04:52 PM, Dennis Lundberg wrote:
Hi Steve,
I can't remember what notation system it uses, but its a different one
than what is usually seen for unix like permissions. It comes from a
component that the plugin uses to perform these operations.
On 2013-01-07 21:49, Steve
Using the assembly plugin I have a file set defined with
644
755
This works correctly - the archive generated has the desired permissions.
But the logging says
[DEBUG] FileSet[outputDir/] dir perms 4 file perms 10
What notation system is this and why does the plugin report it this way
On 11/28/2012 10:13 AM, Steve Cohen wrote:
Is there a way in maven to "echo" some text provided via a property in
pom.xml into a text file at a given location?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apac
Is there a way in maven to "echo" some text provided via a property in
pom.xml into a text file at a given location?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.
On 11/28/2012 09:27 AM, Thomas Broyer wrote:
On Wed, Nov 28, 2012 at 4:06 PM, Steve Cohen wrote:
Are properties defined in pom.xml available in the execution of an assembly
descriptor invoked from pom.xml via the assembly plugin?
I don't think so (TBH, I didn't even try, because I
Are properties defined in pom.xml available in the execution of an
assembly descriptor invoked from pom.xml via the assembly plugin?
If not, is there a way to pass such definitions to the assembly plugin?
-
To unsubscribe, e-ma
Are properties defined in pom.xml available in the execution of an
assembly descriptor invoked from pom.xml via the assembly plugin?
If not, is there a way to pass such definitions to the assembly plugin?
-
To unsubscribe, e-ma
On 01/11/2012 03:22 PM, Rainer Pruy wrote:
But beware that reading "pom.properties" might expose similar problem
as soon as there is a second jar (or some classes directory) with such
file (name).
This is intrinsic to anything that uses getResource*() family of methods
(at least under the hood)
r the hood)
A dirty hack for avoiding that trouble would be to use a file name that
likely is unique to your application.
Rainer
On 11.01.2012 22:13, Steve Cohen wrote:
Thanks for explaining this mysterious result.
I have found that using the pom.properties that Maven creates is a
more strai
what lead me to get an URL from a class that resides with the
same jar and explicitly read that file as outlined in my previous reply)
Rainer
On 11.01.2012 20:41, Steve Cohen wrote:
On 01/11/2012 12:14 PM, Wayne Fay wrote:
getResourceAsStream("META_INF/MANIFEST.MF") and
getResour
On 01/11/2012 12:14 PM, Wayne Fay wrote:
getResourceAsStream("META_INF/MANIFEST.MF") and
getResourceAsStream("/META_INF/MANIFEST.MF") without success even though
I've verified that the file exists in the jar,
Uhh that should be META-INF, right?
Wayne
--
ad(new FileInputStream(manifestFile));
Attributes atts = mf.getMainAttributes();
System.out.println("Version: " +
atts.getValue("Implementation-Version"));
System.out.println("Build: " + atts.getValue("Implementation-Build"));
-Original Message-
On 01/11/2012 10:50 AM, Stephen Connolly wrote:
getClass().getClassLoader().getPackage("").getImplementationVersion()
I really liked the simplicity of this idea. Alas,
ClassLoader.getPackage(String) is a protected method, so this won't help.
Accessible to me is:
Package.getPackage("").get
rom pom
included with jar, provided by a dedicated class to name a few)
Second step would be how you access it from there.
So, probably you can drop a word or more on the use case involved.
Rainer
On 11.01.2012 16:07, Steve Cohen wrote:
It appears that this entire class and the interface it i
() method.
What's going on here and what is the approved method for getting the
application version now?
On 01/11/2012 08:59 AM, Steve Cohen wrote:
Thanks.
But according to this:
http://maven.apache.org/ref/3.0.4-SNAPSHOT/apidocs/org/apache/maven/execution/DefaultRuntimeInformation.html
/maven/execution/DefaultRuntimeInformation.java?av=h
Cheers,
Guillaume
Le 11/01/2012 15:03, Steve Cohen a écrit :
A solution to this question appears to have been offered here, in 2007.
http://maven.40175.n5.nabble.com/HowTo-access-project-version-programmatically-in-application-td82542.html
A solution to this question appears to have been offered here, in 2007.
http://maven.40175.n5.nabble.com/HowTo-access-project-version-programmatically-in-application-td82542.html
It references a page explaining how to do it. That page is now gone:
http://svn.apache.org/repos/asf/maven/componen
I have the following task, which should be simple. I'm having a brain
cramp but I can't figure out how to do it.
I am building a straight java application with dependencies. Under
"normal" circumstances, I can get what I need painlessly by using the
maven assembly plugin and building a jar-w
to this list so they could clarify?
/Anders
On Fri, Dec 2, 2011 at 13:39, Steve Cohen wrote:
On 12/02/2011 01:47 AM, Anders Hammar wrote:
I recognize your situation and here's what I've done for JBoss EAP
(4.3 and 5.0):
For all the runtime artifacts of the platform, I've cre
tion
less good than mine IMO. They claim this will be fixed for the EAP 6.0
repo as Maven will then be used to build the platform. If I recall
correctly they have the correct groupIds and artifactIds though.
Search for "Project Wolf" to find out more.
/Anders
On Thu, Dec 1, 2011 at
I am perplexed by the following situation:
I work for a very large corporation with strict bureaucratic rules about
what you can use. Nonetheless, they have a maven repository
administered by very helpful people. However the maven repository
people don't talk so much to the technical standar
I am perplexed by the following situation:
I work for a very large corporation with strict bureaucratic rules about
what you can use. Nonetheless, they have a maven repository
administered by very helpful people. However the maven repository
people don't talk so much to the technical standar
On 10/12/2011 01:24 PM, Dennis Lundberg wrote:
You can read more about filtering here:
http://maven.apache.org/guides/getting-started/index.html#How_do_I_filter_resource_files
I'll add a link to that page from the page you reference below.
On 2011-10-12 19:43, Steve Cohen wrote:
This i
This is one of the most useless bits of documentation I've ever seen.
http://maven.apache.org/plugins/maven-ejb-plugin/examples/filter-deployment-descriptor.html
HOW would one "inject values into it during the build"?
WHEN in the build process would one do so?
WHY would one need to do so?
An ex
Never mind. WinZip derangement syndrome. The files are there.
On 10/12/2011 11:48 AM, Steve Cohen wrote:
Another clue:
it also says it's adding META-INF/MANIFEST.MF but I don't see that
either. Everything else it says it's adding is there.
On 10/12/2011 11:42 AM, Steve Coh
Another clue:
it also says it's adding META-INF/MANIFEST.MF but I don't see that
either. Everything else it says it's adding is there.
On 10/12/2011 11:42 AM, Steve Cohen wrote:
I am trying to build an EJB Project using maven-ejb-plugin 2.3.
Configuration is absolutely v
I am trying to build an EJB Project using maven-ejb-plugin 2.3.
Configuration is absolutely vanilla with 3.0
With debug output I can see that Maven SAYS it's adding ejb-jar.xml to
the jar but when I look at the built jar, it's not there.
...
[INFO] Building EJB jbsv-ejb-1.0-SNAPSHOT with EJB
my wrote:
2011/9/15 Steve Cohen:
Thanks, I solved this.
There is a bad error on the Tomcat 6.0 documentation website:
http://tomcat.apache.org/tomcat-6.0-doc/manager-howto.html#Configuring_Manager_Application_Access
good catch !
can you load an issue in the tomcat project ?
in which they give
tomcat server and how to configure the latter.
On 09/14/2011 03:17 PM, Olivier Lamy wrote:
Hello,
Do you have any logs in your tomcat ?
Can you try with adding username and password in the mojo
configuration ? (with removing server id).
and
2011/9/14 Steve Cohen:
I am trying to
I am trying to use the Tomcat Maven Plugin
(http://mojo.codehaus.org/tomcat-maven-plugin/) which seems to be
partially migrated to apache, though most of the information is still at
this site.
I am trying to do this because the following "simple" tutorial
instructed me to do so:
http://www
On 02/15/2011 12:58 PM, Steve Cohen wrote:
I can set the permissions of s and s and
s in the maven-assembly-plugin, but it seems from the
online documentation that I can't do so on the . What is more,
when assembling a format, the perms default to 777. At least
that's what I get wh
I can set the permissions of s and s and
s in the maven-assembly-plugin, but it seems from the
online documentation that I can't do so on the . What is more,
when assembling a format, the perms default to 777. At least
that's what I get when I unzip the file (having erased the basedir
previ
Given a project utilizing both the surefire and failsafe plugins, if I
want to run a single integration test but skip the unit tests, is this
possible?
There is a -DskipITs switch but not a -DskipUTs switch.
Thanks
-
To unsub
On 02/04/2011 08:43 AM, Wendy Smoak wrote:
On Fri, Feb 4, 2011 at 9:32 AM, Steve Cohen wrote:
No, there is a POM. I believe I ran mvn:install:install-file and I would
guess that you're right that -DgeneratePom=true is the default because I
know I didn't create a POM myself. This PO
On 02/04/2011 07:24 AM, Wendy Smoak wrote:
On Fri, Feb 4, 2011 at 8:18 AM, Steve Cohen wrote:
Let's say one of my modules (Module A) depends on Hibernate v, X.Y.Z. If I
change some code in one of my own modules (Module B) that depends on Module
A, the system does not go out to the Intern
k the
non-local repos in this situation to see if it has changed?
On 02/03/2011 03:56 PM, Tamás Cservenák wrote:
That's the "-o" CLI switch as "offline".
There is also the "-h" CLI switch for "help". ;)
Thanks,
~t~
On Thu, Feb 3, 2011 at 10:51 PM, S
I am being forced to use maven temporarily in a situation where Internet
access is disallowed. (Don't even ask).
Amazingly by copying an entire local repository from another machine, I
am able to function most of the time. The one problem comes up when
maven wants to look at Maven Central fo
On 01/06/2011 12:32 PM, Steve Cohen wrote:
Of course, this requires that the commented-out modules stay as comments
and not be inadvertently deleted. A better solution might be some sort
of way of indicating this in the modules tag.
Something like:
Module1
com.whatever
Project2
2.0.5
jar
h for more information about our
processes.
Ron
On 06/01/2011 9:51 AM, Steve Cohen wrote:
On 01/06/2011 08:31 AM, Wendy Smoak wrote:
On Thu, Jan 6, 2011 at 9:18 AM, Steve Cohen
wrote:
Set all your versions to end in -SNAPSHOT, that way you can leave them
in the aggregated build without the reposito
On 01/06/2011 08:31 AM, Wendy Smoak wrote:
On Thu, Jan 6, 2011 at 9:18 AM, Steve Cohen wrote:
Set all your versions to end in -SNAPSHOT, that way you can leave them
in the aggregated build without the repository manager complaining on
deploy.
Yes, I suppose I could do that (which is pretty
On 01/06/2011 09:33 AM, Yanko, Curtis wrote:
A not working build doesn't sound simpler to me.
We only use aggregation builds for local builds but our CI just builds
the changed module and then triggers dependent modules up the
architectural chain.
Curt Yanko |
On 01/06/2011 08:31 AM, Wendy Smoak wrote:
On Thu, Jan 6, 2011 at 9:18 AM, Steve Cohen wrote:
Set all your versions to end in -SNAPSHOT, that way you can leave them
in the aggregated build without the repository manager complaining on
deploy.
Yes, I suppose I could do that (which is pretty
On 01/06/2011 08:24 AM, Yanko, Curtis wrote:
Yes, I suppose I could do that (which is pretty much what I
did before), but it sort of defeats the whole purpose of what
I'm trying to accomplish here, which is, be a little more
organized about what is release and what is in development.
Then b
On 01/06/2011 08:18 AM, Steve Cohen wrote:
On 01/06/2011 08:05 AM, Wendy Smoak wrote:
,,,
If one of the modules is stable, do a release of it and have the other
modules depend on that released version (but you can still build the
next snapshot in your aggregator build.)
Is what you are
On 01/06/2011 08:05 AM, Wendy Smoak wrote:
On Thu, Jan 6, 2011 at 8:36 AM, Steve Cohen wrote:
But I would rather not, if possible, redesign my entire build process. I'd
like to be able to modify it to call "mvn deploy" instead of "mvn install".
Of course this
Another dumb newbie question about using maven with a nexus repository.
I have painstakingly developed a build process for a suite of
applications sharing common modules that was based on using local
repositories only. In that setup I blissfully paid zero attention to
version numbers, calling
pting
the passwords. Not two things at the same time.
/Anders
On Thu, Jan 6, 2011 at 01:28, Steve Cohen wrote:
I figured that that must be the case.
Do you have any idea why this would fail? Could the 3.0.1 vs. 2.2.1 thing
be involved or MUST it be that I'm making a mistake I just can
I figured that that must be the case.
Do you have any idea why this would fail? Could the 3.0.1 vs. 2.2.1
thing be involved or MUST it be that I'm making a mistake I just can't see?
On 01/05/2011 05:04 PM, Benjamin Bentmann wrote:
Steve Cohen wrote:
Another thing I notice is
On 01/05/2011 04:36 PM, Steve Cohen wrote:
I am, for the first time, trying to use a nexus repository. I have read
all the information here:
http://maven.apache.org/guides/mini/guide-encryption.html on password
encryption and to the best of my knowledge, have followed it correctly
and set up my
I am, for the first time, trying to use a nexus repository. I have read
all the information here:
http://maven.apache.org/guides/mini/guide-encryption.html on password
encryption and to the best of my knowledge, have followed it correctly
and set up my setting.xml, settings-security.xml and po
1 - 100 of 165 matches
Mail list logo
