think the answer is 'no', which means that the profile shouldn't always
> be active.
> File-based activation of profiles is also used only during build/site
> time, so your workaround seems quite valid to me.
>
> regards,
> Robert
>
> Op Mon, 23 Nov 2015 16:33:17 +0100 schreef Arend v.
at 1:44 PM, Arend v. Reinersdorff <ar...@arendvr.com>
wrote:
> On Sat, Nov 14, 2015 at 11:02 PM, Karl Heinz Marbaise <khmarba...@gmx.de>
> wrote:
>
>> Hi,
>>
>> On 11/14/15 10:06 PM, Arend v. Reinersdorff wrote:
>>
>>> Hi Karl Heinz,
>>>
ing any other profiles. This is more flexible than using the
> -P flag (which I avoid whenever possible).
>
> Regards,
> Curtis
>
> On Sat, Nov 14, 2015 at 3:06 PM, Arend v. Reinersdorff <ar...@arendvr.com>
> wrote:
>
> > Hi Karl Heinz,
> >
> > good poin
On Sat, Nov 14, 2015 at 11:02 PM, Karl Heinz Marbaise <khmarba...@gmx.de>
wrote:
> Hi,
>
> On 11/14/15 10:06 PM, Arend v. Reinersdorff wrote:
>
>> Hi Karl Heinz,
>>
>> good point. I'll try to elaborate more:
>>
>> The idea is to have a p
Hi,
could issue MNG-4533 "Add an always active profile activator" please be
reopened?
https://issues.apache.org/jira/browse/MNG-4533
The issues was automatically closed in 2014.
I find the current workarounds to create an always active profile (check
for non existing property, check for always
${env.TEMP}/${project.groupId}/${project.artifactId}
Best regards,
Arend
On Sat, Nov 14, 2015 at 2:20 PM, Karl Heinz Marbaise <khmarba...@gmx.de>
wrote:
> Hi,
>
> On 11/14/15 2:03 PM, Arend v. Reinersdorff wrote:
>
>> Hi,
>>
>> could issue
.
On Mar 18, 2015, at 9:48 AM, Anders Hammar and...@hammar.net wrote:
That is correct, the docs haven't been updated. Maven 3.3+ requires JDK
1.7.
/Anders (mobile)
Den 18 mar 2015 09:37 skrev Arend v. Reinersdorff ar...@arendvr.com:
Hi,
Maven 3.3.1 requires Java 1.7:
- [MNG-5780
Hi,
Maven 3.3.1 requires Java 1.7:
- [MNG-5780] - upgrade Java minimum version prerequisite from Java 6 to
Java 7
- When I try to run Maven 3.3.1 with Java 1.6 I get the exception:
Exception in thread main java.lang.UnsupportedClassVersionError:
org/apache/maven/cli/MavenCli : Unsupported
On Sun, Jul 7, 2013 at 3:22 PM, Baptiste MATHUS bmat...@batmat.net wrote:
That being said, I'm not sure project.name is guaranteed to fallback to
project.artifactId value. So you might be relying on something unstable
here.
This is a good point. I remember reading somewhere that project.name
On Mon, Jul 8, 2013 at 2:06 PM, Baptiste MATHUS bmat...@batmat.net wrote:
As a side note, I would personnally prefer that there's no such fallback.
I'm not sure I see much value here. In this cas it seems preferable to just
use ${project.artifactId}.
Agreed. I'll do this to fix my project.
? Or is there a reason why I cannot rely on the default value
here?
Regards,
Arend v. Reinersdorff
11 matches
Mail list logo
