More answers inline.
Venkata Krishnan wrote:
Hi Sebastien,
First, many thanks for this very explanatory reply. Please find further
queries below. Thanks.
- Venkat
On 4/8/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Some answers inline.
Venkata Krishnan wrote:
Hi,
I am catching
Hi,
I am catching up with all the work that is going on in 'modules' and am
trying my best join the party. Here are some questions that have come up my
mond... please help me with answers.
- I see that the 'resolve' method in ArtifactProcessor has an argument
'resolver'. Where is this
Some answers inline.
Venkata Krishnan wrote:
Hi,
I am catching up with all the work that is going on in 'modules' and am
trying my best join the party. Here are some questions that have come
up my
mond... please help me with answers.
- I see that the 'resolve' method in ArtifactProcessor
Hi Sebastien,
First, many thanks for this very explanatory reply. Please find further
queries below. Thanks.
- Venkat
On 4/8/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Some answers inline.
Venkata Krishnan wrote:
Hi,
I am catching up with all the work that is going on in
In case you want to see it all working together, SCARuntimeTestCase in the
host-embedded module is a good place to start, it will drive the
contributionServices wired to all dependencies it have.
On 4/8/07, Venkata Krishnan [EMAIL PROTECTED] wrote:
Hi Sebastien,
First, many thanks for this
Thanks Luciano... I will look that up as well.
- Venkat
On 4/9/07, Luciano Resende [EMAIL PROTECTED] wrote:
In case you want to see it all working together, SCARuntimeTestCase in the
host-embedded module is a good place to start, it will drive the
contributionServices wired to all
I have also made some progress on this: I have simplified the
packageProcessors interfaces, making it responsible only for providing a
list of artifacts that need to be processed, and processing now should/will
be driven by the contributionServiceImpl.
I have also started to integrate the
Luciano Resende wrote:
I have also made some progress on this: I have simplified the
packageProcessors interfaces, making it responsible only for providing a
list of artifacts that need to be processed, and processing now
should/will
be driven by the contributionServiceImpl.
I have also
Luciano Resende wrote:
I have committed some new contribution services interfaces under
revision #
525071 that would better align the contribution service module with the
SCDL4J proposals. Note that some of these interfaces, that would be
used for
artifact resolving, will need to be
Hi Sebastien
Your understanding is very right, with the new artifactProcessor
interfaces, we should be able to separate the load phases in multiple phases
as you described.
As for your specific questions, let me try to clarify :
- The assembly module deals with 3 types of files,
[snip]
Luciano Resende wrote:
Hi Sebastien
Your understanding is very right, with the new artifactProcessor
interfaces, we should be able to separate the load phases in multiple
phases
as you described.
As for your specific questions, let me try to clarify :
- The assembly module deals
Jean-Sebastien Delfino wrote:
[snip]
Luciano Resende wrote:
Hi Sebastien
Your understanding is very right, with the new artifactProcessor
interfaces, we should be able to separate the load phases in multiple
phases
as you described.
As for your specific questions, let me try to clarify
I have committed some new contribution services interfaces under revision #
525071 that would better align the contribution service module with the
SCDL4J proposals. Note that some of these interfaces, that would be used for
artifact resolving, will need to be implemented by the Assembly model
13 matches
Mail list logo
