Hi,
Pazmiño Mazón, Iván Andrés wrote:
> I'm using the xdoclet code generation plugin and I need to set the
> generated
> files output folder. to do do, I've set the dir in an attribute:
>
>
>
>
I could imagine the culprit could be artifactory. We were forced to update from
2.2.2 to 2.2.3, otherwise we weren't be able to deploy with maven 3.0 (metadata
issue in Artifactory 2.2.2, deploy worked only in legacy mode). In the meantime
just to be sure, we updated to 2.3.1. But were also requ
There's a couple of potential things in the way you've described it:
- Maven 3.0 does not support non-unique snapshots - you would need to use
timestamps and rely on the repo manager to purge old versions
- if I've misunderstood the above, the difference on timestamps is that Maven
3.0 will actua
I'm using the xdoclet code generation plugin and I need to set the
generated
files output folder. to do do, I've set the dir in an attribute:
I want to insert the filename of one of my project's dependency into a
configuration file via filtering. I can do it in some sloppy fashion
or another, but I wondered if there was a way to get a plugin to set a
definition for me.
Don't know what it should be but I think we may have found a possible
culpret.
Check with Benjamin Bentmann, he'd know what m3 is supposed to do
-Stephen
On 23 November 2010 14:30, Moser, Christian wrote:
> They are from snapshot artifacts. We use non-unique snapshots in
> artifactory.
> The s
2010/11/23 KARR, DAVID (ATTSI) :
> In my "src/main/java" tree, I have properties files that need to be
> deployed into WEB-INF/classes. I thought these would be copied by
> default, but they are not. They didn't go into "target/classes" or
> "WEB-INF/classes". I don't need to filter properties i
In my "src/main/java" tree, I have properties files that need to be
deployed into WEB-INF/classes. I thought these would be copied by
default, but they are not. They didn't go into "target/classes" or
"WEB-INF/classes". I don't need to filter properties in it. I'm using
version 2.1.1 of the mav
On 18/11/2010, at 10:10 AM, Todd Nine wrote:
> Hi Brett,
> There wasn't any version in my pom. I believe I've found the issue.
> I had a repository that connected to github, which is issuing 301
> redirects. This bug is the underlying issue
>
> http://jira.codehaus.org/browse/WAGON-314
>
>
Hi
I have a maven module containing script files which are incrementally
delivered as a zip archive.
I search for a plugin able to zip together all the new or modified files for
a given tag or branch in order to avoid me to do it manually.
Does this plugin exist ? Do you have any suggestion ?
Thx for your help. The state is always resetted between the tests.
My temporary solution for the problem ist to redesign the class. It is not
singleton anymore. Perhaps I will deal with that problem again, later on.
Original-Nachricht
> Datum: Sun, 21 Nov 2010 10:07:19 +0100
>
I'm unable to download the newest artifacts (compiled jar) with maven
3.0 and 3.0.1-RC1 from cmd line. The artifacts were deployed to
artifactory 2.3.1.
After calling "mvn -U" on a dependend artifact, maven just updates the
metadata, but doesn't override the old artifacts contained in the loca
They are from snapshot artifacts. We use non-unique snapshots in artifactory.
The sources are deployed on the same time like the compiled artifacts. So the
timestamp should be equals, shouldn't it?
If not, how could I archieve it?
-Chris
-Ursprüngliche Nachricht-
Von: Stephen Connolly [m
Are these sources of snapshots or releases?
If snapshots it may be that the sources were deployed with a different
timestamp, in which case the maven metadata my not be letting maven 3 find
the artifacts.
IIRC Maven 3 pays more attention to the metadata, whereas Maven 2 might not
trust it as much
I'm unable to download artifact sources with maven 3.0 and 3.0.1-RC1
with following command.
Sources classifier is: -sources (default)
"mvn -U validate dependency:sources -DoverWriteSnapshots=true
-DoverWriteReleases=true"
the artifacts with classifier -sources are available in the l
2010/11/23 Lars Fischer
>
> Is it not possible to use a property inside the pluginManagement section?
>
Sorry, the reason was an another wrong configuration. Everything works fine.
Kind regards,
Lars
Hello,
I would like to define a group of plug-ins inside the pluginManagement
section of a parent pom.
Most of the plugins use the same version, but they also have to be in sync
with other configurations in an second parent pom.
I decided to use a property defining the version. This property is p
2010/11/23 Blanca Hernández :
>> C:\Program Files (x86)
>
> The only difference I remember is this one (I'm also at work, not at home).
> I will try later, because my win7 is also 64.
I installed the 32 bit version of JVM for memory reasons (yeah I know
I can use compressed oops, but at the end th
El 23/11/10 09:54, Antonio Petrelli escribió:
C:\Program Files (x86)
The only difference I remember is this one (I'm also at work, not at
home). I will try later, because my win7 is also 64. The semicolon is
not the problem, I tryed with and without it!
Thanks Antonio!
---
2010/11/23 Blanca Hernández :
> Could you please paste me you enviroments variable configuration??
> I have still the same problem. Thank you for your answers
Sure, I'll take it from my own memory since I tried it at home, and
now I am at work :-D
JAVA_HOME=C:\Program Files (x86)\Java\jdk1.6.0 (I
El 23/11/10 09:46, Antonio Petrelli escribió:
2010/11/22 Antonio Petrelli:
2010/11/22 Blanca Hernández:
With the same error, just changing the path. Somebody told me the could be
maybe Windows7 incompatibilities, do you think so??
No, however to be completely sure I have to check it at home th
2010/11/22 Antonio Petrelli :
> 2010/11/22 Blanca Hernández :
>> With the same error, just changing the path. Somebody told me the could be
>> maybe Windows7 incompatibilities, do you think so??
>
> No, however to be completely sure I have to check it at home this
> evening (CET) where I have a Win
2010/11/22 Blanca Hernández
>
>
> I think this is not the problem, because, I also tryed something like
>
> M2_HOME = C:\apache-maven-2.2.1
>
> With the same error, just changing the path. Somebody told me the could be
> maybe Windows7 incompatibilities, do you think so??
>
Just a little hint, al
23 matches
Mail list logo
