To maillist administrators: I strongly advice to block [EMAIL PROTECTED] They
reply with spam-filter rejects and do not have postmaster email:
http://www.rfc-ignorant.org/tools/lookup.php?domain=netltd.ru
24 ноября 2008 г. 10:11 пользователь <[EMAIL PROTECTED]> написал:
>
> Здравствуйте!
>Ваш
But what I want to do is to use maven assembly to deliver a release version
then put it on other machines where may not have such dependency. How can I
add it to the manifest file?
Stephen Connolly-2 wrote:
>
> system scope implies that the dependency is already on the system
> classpath, so
system scope implies that the dependency is already on the system
classpath, so maven does not need to add it
Sent from my iPod
On 24 Nov 2008, at 04:34, youhaodeyi <[EMAIL PROTECTED]> wrote:
I use maven-jar-plugin to handle the manifest file, see below
configuration:
true
..
Anybody konw this?
2008/11/21 苏林冲 <[EMAIL PROTECTED]>
> Hi, all
> I have set below in setting.xml
>
> com.mycompany.maven.plugins
>
>
> when i run myplugin:exec , maven print these in the console
>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'myp
Здравствуйте!
Ваше письмо принято за спам и удалено.
Если вы считаете это ошибкой, то позвоните пожалуйста по телефону
+7(812)578-09-03 в службу поддержки.
===Вашего письмо===
Return-Path: <[EMAIL PROTECTED]>
Received: from <[EMAIL PROTECTED]>
by inc.ru (CommuniGate Pro RULES 4.1.8)
youhaodeyi wrote:
>
> My project dependent on a snapshot dependency (test-1.0-snapshot). I added
> this configuration in my jar-plugin:
>
> true
> test.ui.Starter
> UI DEMO
>
> All the dependencies will be written to manifest.mf file. So the final
> manifest.mf will includes
I use maven-jar-plugin to handle the manifest file, see below configuration:
true
...
And I have a dependency with system scope:
protocol
protocol
1.0
system
What does your dependency for 2.1.4 look like? I don't see it in the
central repo, at least not in the same groupId as 1.3:
http://repo2.maven.org/maven2/com/lowagie/itext/
If it's in a different groupId, you'll probably want an exclusion for
com.lowagie:itext to get rid of 1.3, and then the depe
It seems displaytag has a dependency for 1.3. When I removed it from my
~/.m2 and told maven to compile offline, it errored on missing it for
displaytag. I don't know why jasperreports is still using this one though.
[INFO] +- displaytag:displaytag:jar:1.1.1:compile
[INFO] | +- com.lowagie:ite
On Sun, Nov 23, 2008 at 5:58 PM, traigo <[EMAIL PROTECTED]> wrote:
> I have an old jar for iText (1.3) that I need to remove. It is being used by
> jasperreports to convert to PDF. I need jasperreports to use the newer
> 2.1.4. I haven't found a way to remove it from maven. I have my pom set to
I have an old jar for iText (1.3) that I need to remove. It is being used by
jasperreports to convert to PDF. I need jasperreports to use the newer
2.1.4. I haven't found a way to remove it from maven. I have my pom set to
require version 2.1.4. I tried to add an exclusion, but version is not
>
> MAVEN REPOSITORY AS ONLY SOURCE OF DEPENDENCIES
I don't see the big issue here , as others have pointed out you can solve
this with a system scope.
On the other hand, setting up your own repository is actually very simple
and gives a lot of advantages (like proper version tracking of the
depe
I guess I might not have been clear: I meant filing an improvement request
especially related to the *documentation* part of maven. If you have to file
another issue about what made you write this plugin to work around the
problem, you're welcome, but that's not what I wad refering to.
Cheers.
20
I might consider raising something in Jira. At the moment I have coded a plugin
to work around this issue.
Do you know if there is any documentation with Maven 2.x that points to a
definite reference of what properties can be referenced.
I haven't managed to find any such documentation on the Ma
I just checked it again. Both work... I tried running
dependency:purge-local-repository before my dependency:tree and it always
seems to work, which actually matches my past experience of the subject.
Am I the only one to find it functional?
Cheers.
Le 23 novembre 2008 17:28, Jeff MAURY <[EMAIL
In order to help, we need to know what steps you took and what error
message you're getting.
I believe OS X ships with Maven 2.0.6, so if you haven't gotten it
completely switched over to (I assume) 2.0.9, the archetype:generate
goal will not be available as Archetype 2 requires at least 2.0.7.
W
Hi,
I am trying to install maven on my mac book, Mac OS X. when i do mvn, it
runs alright; but when i try to do :
mvn archetype:generate .. it gives build failure... My guess is that i am
missing some steps, can someone point me to either a URL or guide me through
the steps for installing this on
Are those artifacts resolved using your local repository or a remote
repository ?
Regards
Jeff MAURY
2008/11/23 Baptiste MATHUS <[EMAIL PROTECTED]>
> I just checked it out again. We have a "blank" project that depends on
> another one with "RELEASE" version, it gave me 2.2.1.alpha01.
> I just sw
On Sat, 2008-11-22 at 22:41 -0800, Bracewell, Robert wrote:
> Is there a property that holds the name of the generated artifact that is
> deployed?
I have been struggling with this need for such a property too.
Unfortunately, the name (and path) of the deployed artifact depends on
the repository
Hi Noah,
Thanks for your report. For your experience not to be lost in the big number
of messages on this list (as you already might have seen), I guess it would
be great you file an improvement in the maven tracker:
http://jira.codehaus.org/browse/MNG.
>From here: http://jira.codehaus.org/secure
Hi,
No, it's not. That's not how maven works. But you can deploy where you want
if you configure it in the settings.xml or directly in the pom.xml.
See http://maven.apache.org/plugins/maven-install-plugin/install-mojo.htmlfor
the options of the Install Mojo.
The localRepository has to be set in th
I just checked it out again. We have a "blank" project that depends on
another one with "RELEASE" version, it gave me 2.2.1.alpha01.
I just switched to LATEST and it gave me "2.2.1.alpha02-SNAPSHOT".
So, it works, at least for me. I'm using maven 2.0.9.
Cheers.
Le 23 novembre 2008 11:50, Jeff MA
On Sat, Nov 22, 2008 at 10:51 PM, Baptiste MATHUS <[EMAIL PROTECTED]> wrote:
> Well, I guess it's simpler than that. And reading the book chapter confirm
> what I already saw when using those keywords on my pom.xml in the past.
> * LATEST will just the latest available version, including snapshots
Hi,
tools from the non Java world like automake and cmake support a
variable DESTDIR:
make install DESTDIR=...
will not install into e.g. /usr/bin but into $DESTDIR/usr/bin. Is
something similar possible with mvn? I want the artifacts to be
installed into ${destdir}/${settings.localRepository}
OK thanks. This is a smart method.
Stephen Connolly-2 wrote:
>
> ok, try this
>
> create a dummy-jar module that has your system scope as its
> dependency. this dummy jar will be empty
>
> now add the dummy jar as a test scope dependency. your system scope
> transitive dependency will ther
you can also vote for
https://issues.apache.org/jira/browse/COMMONSSITE-24to get this fix ... in
future ;)
2008/11/23 nicolas de loof <[EMAIL PROTECTED]>
> I suggested on commons-dev to add sources-jars for all commons-* releases
> that didn't had one, but discution went to licencing and Apache r
I suggested on commons-dev to add sources-jars for all commons-* releases
that didn't had one, but discution went to licencing and Apache release
rules, so there was no consensus and nothing in repo.
You can get much of them from
http://people.apache.org/~nicolas/missing-commons-sources.jar/
WARNIN
ok, try this
create a dummy-jar module that has your system scope as its
dependency. this dummy jar will be empty
now add the dummy jar as a test scope dependency. your system scope
transitive dependency will therefor be added to the test compile
classpath
Sent from my iPod
On 23 Nov 2
28 matches
Mail list logo
