Hi all,
I'm having a problem with a multi-module project where one of the modules is
an annotation-based maven-plugin: https://github.com/fommil/netlib-java/
Basically, "mvn compile" fails the first time with
Could not find goal 'interface' in plugin
org.netlib:generator:1.0-SNAPSHOT among ava
If you are not izpack user, then dont use izpack-maven-plugin
Here are steps you can do
1. Use maven dependency to copy your 'zip' resource into your resource
directory so that your final jar can include it
2. At mojo run time, you can copy the zip out of your plugin jar to a
temp place, th
Great.
Ron
On 25/06/2013 3:11 PM, igor.zaplet...@gmail.com wrote:
Yes, IzPack is actually that I need. Thanks Ron.
On Jun 25, 2013, at 10:52 PM, Ron Wheeler
wrote:
On 25/06/2013 2:30 PM, Igor Zapletnev wrote:
Thanks for quick response! I want to include zip file in the resources dir for
e
Yes, IzPack is actually that I need. Thanks Ron.
On Jun 25, 2013, at 10:52 PM, Ron Wheeler
wrote:
> On 25/06/2013 2:30 PM, Igor Zapletnev wrote:
>> Thanks for quick response! I want to include zip file in the resources dir
>> for example. I want to have an access to this zip file in my mojo.
>
On 25/06/2013 2:30 PM, Igor Zapletnev wrote:
Thanks for quick response! I want to include zip file in the resources
dir for example. I want to have an access to this zip file in my mojo.
Call copy-dependency pragmatically is not clear for me because I don't
want resolve this dependencies during
Thanks for quick response! I want to include zip file in the resources dir
for example. I want to have an access to this zip file in my mojo.
Call copy-dependency pragmatically is not clear for me because I don't want
resolve this dependencies during runtime each time. I want to copy this
dependenc
Where in the jar (path) would you like to put the zip?
Why?
What are you actually constructing?
Have you looked at the Assembly plug-in or at building your final
artifact with an installer.
Ron
On 25/06/2013 2:01 PM, Igor Zapletnev wrote:
To be more clear – I want to include this zip artifac
To be more clear – I want to include this zip artifact in my jar file.
Thanks for help again.
On Tue, Jun 25, 2013 at 9:36 PM, Igor Zapletnev wrote:
> But is it possible to get an access to the zip file directly without
> unzipping?
>
>
> On Mon, Jun 24, 2013 at 10:05 PM, Wayne Fay wrote:
>
>>
But is it possible to get an access to the zip file directly without
unzipping?
On Mon, Jun 24, 2013 at 10:05 PM, Wayne Fay wrote:
> > How would you unzip a static zip file rather than a Maven artifact?
>
> First, you'd make it a Maven artifact. A useful blog post on this subject:
>
> http://de
Hi,
currently, I am facing a problem with the javadoc plugin: It seems that
the plugin tries to download connected dependencies (that are used in our
type hierarchy) from repo1 (central) although we have a defined mirror for
that in the settings. Can I specify mirrors for plugins somewhere in t
Hi Virg,
virg g wrote:
> Yes you are absolutely right, I totally agree with you. I am asked to
> implement these kind of builds.
Ahh, OK. Nothing helps against ignorance in the business layer ;-)
- Jörg
-
To unsubscribe, e-ma
Yes you are absolutely right, I totally agree with you. I am asked to
implement these kind of builds.
On Tue, Jun 25, 2013 at 3:35 PM, Jörg Schaible
wrote:
> Hi Virg,
>
> virg g wrote:
>
> > Yes. We have multiple customers, some of them support 1.5 and others 1.6.
> > We need to release both the
Hi Virg,
virg g wrote:
> Yes. We have multiple customers, some of them support 1.5 and others 1.6.
> We need to release both the builds with 1.5 and 1.6.
[snip]
sorry, in this case it simply does not make sense to use different JDKs. If
you are able to compile the same sources for JDK 1.5 and
Well, if you have multiple customers, some on 1.5, some on 1.6, then just
release a 1.5 version.
It will work perfectly with both 1.5 AND 1.6.
Please note this is actually what you certainly are already doing with a
lot of dependencies in your classpath. Not all have the same bytecode
version.
Wh
Yes. We have multiple customers, some of them support 1.5 and others 1.6.
We need to release both the builds with 1.5 and 1.6. Right now i am
initiating build separately one after the other, setting JAVA_HOME
correctly and passing jdk-version according build i need, this parameter i
am setting for
Hi,
+1 on the question, do you really need to build for both versions? As JDK
is backward compatible, you could for example build only with 1.5.
Maybe you only want to test your build on a 1.5 and 1.6, then I personally
would prefer keeping a quite simple build and keep those combinations on
some
16 matches
Mail list logo
