I'm afraid I don't understand what you are proposing.
Ralph
On Jul 26, 2011, at 4:43 PM, Jörg Schaible wrote:
> Hi Ralph,
>
> Ralph Goers wrote:
>
>> For some reason Christian's message didn't arrive in the proper email
>> folder so I never saw it.
>>
>> Actually, the real problem here isn't
Hi Ralph,
Ralph Goers wrote:
> For some reason Christian's message didn't arrive in the proper email
> folder so I never saw it.
>
> Actually, the real problem here isn't as much the LICENSE and NOTICE files
> as it is checkstyle.xml. It would be bad to have copy of that file in
> each sub-fold
For some reason Christian's message didn't arrive in the proper email folder so
I never saw it.
Actually, the real problem here isn't as much the LICENSE and NOTICE files as
it is checkstyle.xml. It would be bad to have copy of that file in each
sub-folder as the checkstyle rules would be li
Christian Grobmeier wrote:
> OK, then the mvn eclipse plugin 2.8 will fail when building it because
> it does not support ".." path. Should we nail down the mvn-eclipse
> version to 2.7 in the pom? We have something similar for the idea
> plugin in the parent pom.
>
> The other question is, if it
OK, then the mvn eclipse plugin 2.8 will fail when building it because
it does not support ".." path. Should we nail down the mvn-eclipse
version to 2.7 in the pom? We have something similar for the idea
plugin in the parent pom.
The other question is, if it is really a good idea to depend a sub
p
Also, the change was incorrect as it was using basedir to locate the NOTICE and
LICENSE files. basedir will refer to the core subproject, not the project root,
which is where those files are located.
On Jul 24, 2011, at 12:14 PM, Ralph Goers wrote:
> I need to revert this. It breaks the site bu
I need to revert this. It breaks the site build.
Ralph
On Jul 24, 2011, at 6:30 AM, Christian Grobmeier wrote:
> Thanks, it helped.
>
> Found out that m3 eclipse plugin 2.8 is not so good with relative
> paths as 2.7 was.
> i replaced the ".." path in the vfs-core with ${basedir}
>
> Hope that
Thanks, it helped.
Found out that m3 eclipse plugin 2.8 is not so good with relative
paths as 2.7 was.
i replaced the ".." path in the vfs-core with ${basedir}
Hope thats ok for everybody, I am not a core committer to this component
On Sun, Jul 24, 2011 at 2:13 PM, Gary Gregory wrote:
> I've n
I've not seen this exact issue but this kind of problem is not
uncommon with M3 compared to M2. You could try Running clean and then
upgrading to the latest common-parent. After that you can try
upgrading the plugins that blow up one at a time. The catch 22 is
that newer plugins might not work in
