right, this is a limitation recently introduced in WTP.
Either reimport your project in eclipse as a Maven project after removing
all .project and .settings/ files
or open .settings/org.eclipse.wst.common.project.facet.core.xml and change
the jst.ear facet to <installed facet="jst.ear" version="6.0"/>


On Mon, Jan 6, 2014 at 7:25 PM, Marcus Malcom <malcomm...@gmail.com> wrote:

> Thanks for the quick response. When I attempt that change, I get:
>
> Cannot change version of project facet EAR to 6.0
>
>
> I'm not seeing any options to allow for this.
>
>
> On Mon, Jan 6, 2014 at 10:03 AM, Fred Bricon <fbri...@gmail.com> wrote:
>
>> initialize-in-order is a Java EE6 feature, so you need to tell maven to
>> generate the corresponding application.xml. try :
>>
>>             <plugin>
>>                 <artifactId>maven-ear-plugin</artifactId>
>>                 <version>2.8</version>
>>                 <configuration>
>>                     <version>6</version>
>>                     *<initializeInOrder>true</initializeInOrder>*
>>                 </configuration>
>>             </plugin>
>>
>> Check that target/m2e-wtp/ear-resources/application.xml contains
>>  <initialize-in-order>true</initialize-in-order>
>> This is what should be deployed to Glassfish.
>>
>>
>>
>>
>> On Mon, Jan 6, 2014 at 6:41 PM, Marcus Malcom <malcomm...@gmail.com>wrote:
>>
>>> Eclipse Version: Kepler Service Release 1
>>> Build id: 20130919-0819
>>> m2e version: 1.4.0.20130601-0317
>>>
>>> I have an EAR project (project is multi module maven project) and when I
>>> attempt to deploy from Eclipse to a GlassFish server (3.1), the EAR project
>>> is showing up correctly; however, the modules being deployed are not in the
>>> correct order. In the EAR project, I have this:
>>>
>>> <project>
>>>     <build>
>>>         <plugins>
>>>             <plugin>
>>>                 <artifactId>maven-ear-plugin</artifactId>
>>>                 <version>2.8</version>
>>>                 <configuration>
>>>                     *<initializeInOrder>true</initializeInOrder>*
>>>                 </configuration>
>>>             </plugin>
>>>         </plugins>
>>>     </build>
>>> </project>
>>>
>>> The initializeInOrder appears not be respected. Any ideas?
>>>
>>> Thanks,
>>>
>>> Marcus
>>>
>>>
>>>
>>> _______________________________________________
>>> m2e-users mailing list
>>> m2e-users@eclipse.org
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>
>>>
>>
>>
>> --
>> "Have you tried turning it off and on again" - The IT Crowd
>>
>> _______________________________________________
>> m2e-users mailing list
>> m2e-users@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>
>>
>
> _______________________________________________
> m2e-users mailing list
> m2e-users@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
>


-- 
"Have you tried turning it off and on again" - The IT Crowd
_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to